Comments on: Opinionated Input Builders for ASP.Net MVC – Part 2 Html Layout for the Label

By: erichexter

erichexter — Thu, 11 Jun 2009 13:10:44 +0000

@Alexander, the actual validation is a seperate concern which would probably be tied into your model binder. But the portion of this framework in the convention could implement your own convention which could query the model and determine things like required fields. The actual Validation in the UI are helpers around displaying the messages that are stored in the model state the is already part of the MVC framework. This just ties the layout of these together.

@Haacked, Busted… I will update my example and source.

By: Haacked

Haacked — Thu, 11 Jun 2009 04:35:02 +0000

Eric, you should Html Encode the Model.Name and Model.Label in your snippet.

By: Alexander Byndyu

Alexander Byndyu — Thu, 11 Jun 2009 04:24:39 +0000

Why SimpleModel object can know about self-validation? I think we need SimpleModelValidator and add IHasValidation to impleModel object.

By: erichexter

erichexter — Wed, 10 Jun 2009 19:59:25 +0000

@Duncan,, I think you are totally getting it. If you look at the Part 4 there is a static func that is the extensibility point to each of these properties. That is where you could implement _your_ conventions. I guess I have spent more time explaining how to configure the exceptions rather than explaining the Convention based approach….. Which is actually the most powerful part of this.

By: Duncan Godwin

Duncan Godwin — Wed, 10 Jun 2009 19:52:32 +0000

Looking at this I’m now wondering about conventions that can just be applied globally as defaults rather than per property. e.g.
- Format all dates in this way, with this control and use this validator.
- Any property called Html or Comment give a multi-line text field.
- Setup convention validation for all e-mail addresses for properties that contain Email.
- All fields called Name are required.

Maybe I’m pushing it a little now

By: erichexter

erichexter — Wed, 10 Jun 2009 14:14:27 +0000

@Eduardo, the builders support my default convention.. but allow you do plugin your own convention.. The next post will show how to change the convention for the partial view selection but the approach is the same for each element. As long as you can define a way to determine how to find your resource key from a PropertyInfo object representing each property than it is a pretty simple convention to implement.

By: Eduardo Miranda

Eduardo Miranda — Wed, 10 Jun 2009 13:53:41 +0000

Hi Eric,

Cool stuff you are building.

One question: Do you have a solution for multi-language UIs? Using .NET resources maybe?

By: Remco Ros

Remco Ros — Wed, 10 Jun 2009 11:44:55 +0000

Looks nice,

looking forward to see some implementation details.

By: erichexter

erichexter — Wed, 10 Jun 2009 11:11:38 +0000

@Nigel, The attributes I am using here actually are DataAnnotations attributes. the PartialView inherts from the UIHint for example. I just wanted to provide a syntactically clean …ie no training required way of applying the convention. The patial view code does look for a UIHInt rather than a PartialView attribute.

@sarong I will get the source zipped up and uploaded this morning.

By: sarong

sarong — Wed, 10 Jun 2009 10:47:59 +0000

source code would make it possible to give some feedback