Comments on: MVC and LightSpeed – Part 4 – Model Binding

By: Jeremy Boyd

Jeremy Boyd — Wed, 02 Sep 2009 03:03:06 +0000

Hi Grayson – the EntityModelBinder class is part of the community code solution which you can grab via SVN from here: https://code.mindscape.co.nz/repos/LightSpeed/Mvc/Trunk – you will want to compile this against whichever version of LightSpeed you are currently using

Alternatively you can just repurpose the class to your own needs and include it directly in your MVC app.

Jeremy

By: grayson mitchell

grayson mitchell — Wed, 02 Sep 2009 02:38:43 +0000

A comment on putting what you have discussed into practice re Model Binder. I am doing a ‘quick’ evaluation of Lightspeed for work, and as part of that I wanted to implement a model binder (as in Linq to sql this happens out of the box).
So your blog looked to be just what I needed. However there are a couple of issues.
1\ Links to the source code are a little unclear (there is a link to EntityModelBinder.cs, which uses Mindscape.LightSpeed.Mvc.Helpers – so is not usable on its own – for example)
2\ The FilmFestival example code is written in a later version of Lightspeed than production – the Mindscape.LightSpeed.Mvc.dll requires later version of Lightspeed.

By: Tutoriales ASP.NET MVC de Mindscape « Mi Blog

Tutoriales ASP.NET MVC de Mindscape « Mi Blog — Fri, 20 Mar 2009 08:21:18 +0000

[...] MVC and LightSpeed – Part 4 – Model Binding Blogged with the Flock Browser [...]

By: jeremy

jeremy — Thu, 19 Mar 2009 23:38:53 +0000

Hi Jake

We generally code gen DTO’s, and based on feedback we have added this in to the LightSpeed designer to auto-gen these if you need them.

In terms of the scenario where you need to touch the database to validate, this would be the case for a [ValidateUnique] field – LightSpeed handles this internally for you so generally you dont need to worry about it directly.

Assuming this isnt the case, it sounds more like some additional validation logic to be performed in the Controller action.

LightSpeed entities also have an OnValidate() which you can override with any custom validation code as required – this is inline with pretty much every other validation framework

By: Jake Scott

Jake Scott — Thu, 19 Mar 2009 23:28:09 +0000

I like how tidy the controller logic is and seems to be inline with the single responsibility principle. How would you handle a scenario where the model object needs to touch the database to know if it is valid – for example having a unique email address? On a recent project I used ViewModel objects decorated with Validation Attributes (kinda like DTO’s) to handle user input. Then if valid I would pass these objects of to a service layer to co-ordinate domain validation and mapping of the DTO’s to the Model objects. Worked alright but I think I will use a automapper in the future for this, or I know you guys codegen DTO objects or something.

By: DotNetShoutout

DotNetShoutout — Thu, 19 Mar 2009 22:44:04 +0000

ASP.NET MVC Tutorial Part 4: Model binding and easy validation with xVal and LightSpeed…

Thank you for submitting this cool story – Trackback from DotNetShoutout…