Comments on: Opinionated Input Builders for ASP.Net MVC – Part 5 the Required input http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/ Wed, 19 Jun 2013 06:32:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: erichexter http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-166 erichexter Sat, 27 Jun 2009 20:54:11 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-166 @sean, you would need to implement your own convention and wire it in at application start up. The convention would use service location to create a class that can look into web context and determine the user of the current request and than return the appropriate value. @sean, you would need to implement your own convention and wire it in at application start up. The convention would use service location to create a class that can look into web context and determine the user of the current request and than return the appropriate value.

]]> By: Sean http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-165 Sean Sat, 27 Jun 2009 18:38:45 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-165 How would the attribute-based approach extend to situations where you wanted to make required|NOTrequired configurable based on the user role, or perhaps even at an application instance level? How would the attribute-based approach extend to situations where you wanted to make required|NOTrequired configurable based on the user role, or perhaps even at an application instance level?

]]> By: erichexter http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-164 erichexter Fri, 26 Jun 2009 01:13:01 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-164 @Scott in this sample I am actually using the DataAnnotations Model Binder and the preview of the DataAnnotations dll from the Mvc Release on codeplex. I wanted to demonstrate that this method of implementing the Opinions lets the developer choose their approach and use this framework to plug in an attribute based approach or a code based approach. I think that which ever approach is used it has to be tied into the validation and model binder. @Scott in this sample I am actually using the DataAnnotations Model Binder and the preview of the DataAnnotations dll from the Mvc Release on codeplex. I wanted to demonstrate that this method of implementing the Opinions lets the developer choose their approach and use this framework to plug in an attribute based approach or a code based approach. I think that which ever approach is used it has to be tied into the validation and model binder.

]]> By: Scott Hanselman http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-163 Scott Hanselman Thu, 25 Jun 2009 22:57:28 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-163 Wouldn't you then need to create or extend the DefaultModelBinder to make sure that the length, required, and other attributes on the ViewModel are respected on the way IN to a method after a POST? Wouldn’t you then need to create or extend the DefaultModelBinder to make sure that the length, required, and other attributes on the ViewModel are respected on the way IN to a method after a POST?

]]> By: erichexter http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-162 erichexter Wed, 17 Jun 2009 16:51:17 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-162 @Roberto, This is on my list to implement. I could see the convention calling into a chain of responsibilities provider that could decide to pull the appropriate data from a repository. that being said I do need to get that example put in so that it is clear how to extend it and get some feedback to improve on the design. @Roberto, This is on my list to implement. I could see the convention calling into a chain of responsibilities provider that could decide to pull the appropriate data from a repository. that being said I do need to get that example put in so that it is clear how to extend it and get some feedback to improve on the design.

]]> By: Roberto Hernandez http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-161 Roberto Hernandez Wed, 17 Jun 2009 15:35:40 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-161 You are missing the classical DropDownList using referencial data from a data store. I know that it can be done using the partial views scenario, but I still would love to see a good sample on how to implement it and how it affects the design of your ViewModel. Regards, Roberto.- You are missing the classical DropDownList using referencial data from a data store. I know that it can be done using the partial views scenario, but I still would love to see a good sample on how to implement it and how it affects the design of your ViewModel.

Regards,

Roberto.-

]]> By: erichexter http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-160 erichexter Fri, 12 Jun 2009 00:17:17 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-160 @Tad there has been zero performance work done on this so far. As they stand i am sure that their are some areas that would not scale very well under high load. I still need to address that but I am certain that with some profiling the any performance problems could be worked through so that the gain in productivity and consistency of your application will far out weigh the performance penalty you pay for using this type of control selection. Under the hood the code goes through the lambda expressions and than uses reflection to get the value of the property from the model. I know there are performance penalties with this type of access. I also know that their are a few different ways to overcome this through IL generation and caching of compiled expressions. So in the long term I am not worried because there are some well defined ways to deal with those issues. But until I do the performance testing I do not want to start optimizing any of the code. @Tad there has been zero performance work done on this so far. As they stand i am sure that their are some areas that would not scale very well under high load. I still need to address that but I am certain that with some profiling the any performance problems could be worked through so that the gain in productivity and consistency of your application will far out weigh the performance penalty you pay for using this type of control selection.

Under the hood the code goes through the lambda expressions and than uses reflection to get the value of the property from the model. I know there are performance penalties with this type of access. I also know that their are a few different ways to overcome this through IL generation and caching of compiled expressions. So in the long term I am not worried because there are some well defined ways to deal with those issues. But until I do the performance testing I do not want to start optimizing any of the code.

]]> By: Tad http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-159 Tad Thu, 11 Jun 2009 22:11:59 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-159 What are the performance implications of that opinionated helpers? What are the performance implications of that opinionated helpers?

]]> By: erichexter http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-158 erichexter Thu, 11 Jun 2009 17:43:39 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-158 @Bill Barry If you look in the source code I have one view which has the following form <%=Html.InputForm("Home","Save")%> The Model does not have to be specified as it can be obtained from the HtmlHelper. I am not sure what part of the series I will get to that one but I do have it working.. It was a natural progression once the other pieces of the builder came together. @Bill Barry If you look in the source code I have one view which has the following form < %=Html.InputForm("Home","Save")%> The Model does not have to be specified as it can be obtained from the HtmlHelper. I am not sure what part of the series I will get to that one but I do have it working.. It was a natural progression once the other pieces of the builder came together.

]]> By: Bill Barry http://lostechies.com/erichexter/2009/06/11/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input/#comment-157 Bill Barry Thu, 11 Jun 2009 16:14:33 +0000 /blogs/hex/archive/2009/06/10/opinionated-input-builders-for-asp-net-mvc-part-5-the-required-input.aspx#comment-157 I agree, which is why I would use just the first bit from my example. Unfortunately not everybody thinks like I do. The part I am talking about to suggest that this is all that should be done for 90% of all forms: <%=Html.ValidationSummary()%> This sample demonstrates ... <% Html.Form<SimpleModel>("save", "home"); %> perhaps with default values being provided: <% Html.Form("save", "home", Model); %> I agree, which is why I would use just the first bit from my example. Unfortunately not everybody thinks like I do.
The part I am talking about to suggest that this is all that should be done for 90% of all forms:
< %=Html.ValidationSummary()%>
This sample demonstrates …
< % Html.Form(“save”, “home”); %>

perhaps with default values being provided:
< % Html.Form("save", "home", Model); %>

]]>