I found there was no need for helper methods, extra code or looping through the collection. I just used the following: @Html.DisplayNameFor(model => model.Carriers.FirstOrDefault().Name) This still works even if FirstOrDefault() would return null because it’s only looking for meta data, the Name property itself is not accessed. Many thanks to @Kurian who inspired this answer.
I was also experiencing the same issue. When I debug the Action and look at the ModelState.Values[1].Errors[0].Exception for example, I see the following: {“The parameter conversion from type ‘System.String’ to type ‘System.Collections.Generic.KeyValuePair`2[[System.String, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Int64, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]’ failed because no type converter can convert between these types.”} System.Exception {System.InvalidOperationException} In my scenario, … Read more
Not sure if this is new to mv4 or if it exists in prior version. But the DropDownListFor includes an additional parameter for the SelectList Constructor. SelectList(IEnumerable, String, String, Object) For example: Html.DropDownListFor( x => x.Countries[ i ], New SelectList(Model.CountryList,”ID”,”Description”,Model.Countries[i])) Where ID is the Country ID in the CountryList object and Description is the Country … Read more
An input field marked with the disabled=”disabled” attribute NEVER sends its value to the server. If you want to achieve this you could use the readonly=”readonly” attribute which still prevents the user from modifying the value but sends the existing value when the form is submitted.
I use HtmlHelpers all the time, most commonly to encapsulate the generation of boilerplate HTML, in case I change my mind. I’ve had such helpers as: Html.BodyId(): generates a conventional body id tag for referencing when adding custom css for a view. Html.SubmitButton(string): generates either an input[type=submit] or button[type=submit] element, depending on how I want … Read more
I am afraid that this is not possible. Unfortunately the WebGrid it doesn’t support the same syntax as standard HTML helper such as TextBoxFor where you could: @Html.TextBoxFor(x => x.SomeProp, new { data_test = “testdata” }) and the underscore would be automatically converted to dash.
Here’s another article that shows you how to achieve the same thing: public static HtmlHelper CreateHtmlHelper(ViewDataDictionary vd) { var mockViewContext = new Mock<ViewContext>( new ControllerContext( new Mock<HttpContextBase>().Object, new RouteData(), new Mock<ControllerBase>().Object), new Mock<IView>().Object, vd, new TempDataDictionary()); var mockViewDataContainer = new Mock<IViewDataContainer>(); mockViewDataContainer.Setup(v => v.ViewData).Returns(vd); return new HtmlHelper(mockViewContext.Object, mockViewDataContainer.Object); }
In addition to PanJanek’s answer: If you don’t really need the elements to have an id, you can also specify id=”” in the htmlAttributes (i.e. new { id=”” }) parameter of helpers. This will result in the id attribute being left out completely in the generated html. source: https://stackoverflow.com/a/2398670/210336
Well, if you’ve decorated your models with the DisplayNameAttribute like this: [DisplayName(“First Name”)] string FirstName { get; set; } Then you only specify what the text of the label would be in one place. You might have to create a similar label in number of places, and if you ever needed to change the label’s … Read more
Description You can use another overload of the DropDownList method. Pick the one you need and pass in a object with your html attributes. Sample @Html.DropDownList(“CategoryID”, null, new { @onchange=”location = this.value;” }) More Information MSDN – SelectExtensions.DropDownList Method