LightSpeed, Validation and .NET 4

Hello,

Any chance LightSpeed can ship assemblies compiled against the .NET 4 framework and support the validation infrastructure provided by .NET 4.0? Having two different and incompatible validation models is time consuming and problematic.

Thanks, Werner

We're continuing to monitor whether it's worth producing a .NET 4-specific build, but at the moment the .NET 3.5 build works fine in .NET 4 except for a SQLite issue that can be worked around in configuration, so we don't have immediate plans.

We do not plan to switch over to the DataAnnotations validation infrastructure. We provide an adapter which enables DA consumers to use LightSpeed validations. See the "Validation" section in http://www.mindscapehq.com/documentation/lightspeed/Building-Web-Applications-/Building-ASPNET-MVC-Applications, or for the more general case the EntityDataAnnotationProvider class (for usage example see http://www.mindscapehq.com/documentation/lightspeed/Building-Web-Applications-/ASPNET-Dynamic-Data). If you install this as a metadata provider as per the ASP.NET Dynamic Data example, then your components which use DataAnnotations should be able to work with LightSpeed validations with no additional effort on your part.

Both of those links assume I'm exposing my entities as-is on a website. However, this isn't my only scenario. I'd like a simple assembly with a single way to validate whether entities are correct. This ensures better reuse across all the consumers of that assembly, including web applications, WCF services and windows applications.

I think I'll avoid LightSpeed validation, it has just caused too many headaches in the past couple of months.

Werner