Buu Nguyen's Blog

This is truly a month of release. In fact, I released Fasterflect 2.0 and Combres 2.0 within the past 10 days. And now, it’s ASP.NET MVC Validation Library 1.3. It’s not like I suddenly have all the time in the world to push the releases of these libraries. Instead, code gets accumulated over the last 3-4 months until they happen to be done at the same time. Anyway, a couple of notes about this release of ASP.NET MVC Validation Library.

First and foremost, if you are using ASP.NET MVC 2.0, then you can stop reading. This library is not for you. Really, ASP.NET MVC 2.0 comes with a highly robust and flexible validation functionality built-in already, so there’s no reason to look for a 3rd-party library which has nothing more to offer. That said, if you are still stuck with some ASP.NET MVC 1.0 legacy apps, like me, then my library can be useful.

If you are not familiar with this library, please refer to this originally introductory post to learn how to use it. Because I haven’t taken the time to posted about the all of changes since the release mentioned in that post, I’m doing it now.

Changes in 1.3

• Support custom server-side validation
• Support remote validation (integrated with jQuery Validate’s remote method)
• The design of validation attributes is improved to make addition of new validation attribute much more intuitive

Changes in 1.2

• Support RegularExpressionValidatorAttribute (use the property ClientFunctionName to specify the corresponding jQuery Validate’s function)
• Allow specify a custom form validation function (i.e. instead of the default $(formName).validate())
• Support PropertyComparisonValidatorAttribute (equal operator only)
• EntityValidationException adds constructor to accept custom key-value pair (i.e. useful for non-model/custom validations)
• Support specifying custom ready function (i.e. useful when using a 3rd-party script loader, like Google’s, to load jQuery)
• Support specifying custom client ID (in case the client-side ID is different from the client-side name (used for posted value)

Changes in 1.1

• Eliminate the need to specify type parameter when invoking Validate() method
• Allow users to specify prefix when populating model state with error messages

That’s it for the post. That’s it? Yes, that’s it. The library is ridiculously easy to use, so you don’t need another 10 pages of tutorial here. Instead, the old introductory article, together with the above change notices, should be enough for you to start working with the library. Okay, it might not be that easy. Don’t worry yet, the download of ASP.NET MVC Validation Library comes with CHM API documentation and a sample application that uses almost all features of the library. So, download and explore the library yourself. And post here if you have any comment or feedback. Enjoy!