I am working on an ASP.NET MVC-4 web application. I'm defining the following inside my action method to build a SelectList
:
ViewBag.CustomerID = new SelectList(db.CustomerSyncs, "CustomerID", "Name");
Then I am rendering my DropDownListFor
as follow inside my View
:
@Html.DropDownListFor(model => model.CustomerID, (SelectList)ViewBag.CustomerID, "please select")
As shown I am naming the ViewBag
property to be equal to the Model
property name which is CustomerID
. From my own testing, defining the same name didn't cause any problem or conflict but should I avoid this ?
There is not harm to use it. You will not get any error. but best practice is to bind model property.
You should not use the same name for the model property and the
ViewBag
property (and ideally you should not be usingViewBag
at all, but rather a view model with aIEnumerable<SelectListItem>
property).When using
@Html.DropDownListFor(m => m.CustomerId, ....)
the first"Please Select"
option will always be selected even if the value of the model property has been set and matches one of the options. The reason is that the method first generates a newIEnumerable<SelectListItem>
based on the one you have supplied in order to set the value of theSelected
property. In order to set theSelected
property, it reads the value ofCustomerID
fromViewData
, and the first one it finds is"IEnumerable<SelectListItem>"
(not the value of the model property) and cannot match that string with any of your options, so the first option is selected (because something has to be).When using
@Html.DropDownList("CustomerId", ....)
, nodata-val-*
attributes will be generated and you will not get any client side validationRefer this DotNetFiddle showing a comparison of possible use cases. Only by using different names for the model property and the
ViewBag
property will it all work correctly.