Better solution without exluding fields from Binding

Question

I have an entity Movie that has 2 fields(poster and trailer) of varbinary(max) within the database. When I want to create the instance on the controller I had a lot of problem trying to get those fields from the View, finally, I got this solution:

[HttpPost]
public ActionResult Create([Bind(Exclude = "poster, trailer")]Movie movie, HttpPostedFileBase poster, HttpPostedFileBase trailer)

Any one has a better solution for this binding, just to get something like this?:

public ActionResult Create(Movie movie)

I need "poster" and "trailer" fields that they come with the post action too

I assume `poster` and `trailer` are the names you gave to your `` elements? — Tieson T., Dec 31 '13 at 23:32

score 1 · Answer 1 · edited May 23 '17 at 10:32

1

You should not use your domain models in your views. ViewModels are the correct way to do it.

You need to map your domain model's necessary fields to viewmodel and then use this viewmodel in your controllers. This way you will have the necessery abstraction in your application.

If you never heard of viewmodels, take a look at this.

edited May 23 '17 at 10:32

Community

1
1

answered Dec 31 '13 at 23:33

emre nevayeshirazi

18,983
12
64
81

score 1 · Accepted Answer · answered Jan 01 '14 at 04:55

Use a view model

public class MovieModel
{
    public HttpPostedFileBase Poster { get; set; }
    public HttpPostedFileBase Trailer { get; set; }
}

The in your controller

[HttpGet]
public ActionResult Create()
{
    return View(new MovieModel());
}

[HttpPost]
public ActionResult Create(MovieModel movie)
{
    var entity = new Movie();

    using (var memoryStream = new MemoryStream())
    {
        movie.Poster.InputStream.CopyTo(memoryStream);
        entity.Poster = memoryStream.ToArray();
    }

    using (var memoryStream = new MemoryStream())
    {
        movie.Trailer.InputStream.CopyTo(memoryStream);
        entity.Trailer = memoryStream.ToArray();
    }

    dbContext.Movies.AddObject(entity);
    return View("index");
}

Better solution without exluding fields from Binding

2 Answers2