Project Validation Everywhere´s purpose is to create a framework for declarative validation, so you can use the same validation logic through all the different environments that your Business Layer might be running against.

This project started mainly because of NMVP project (NMVP Project). I do a lot of MVP UI´s, and they really help in the direction of creating UI unit tests. One part of the UI that is overlooked in the testing is the validation since it´s done by ASP.Net and it´s validators.

We all know that the validators work beautifully, but what about the Custom Validators, and Regex Validators, and Data Compare Validators? Are they being used correctly. If you have to redo the same Validation structure in the Unit Test it gives you another chance to check the validation rules and then, once you´ve built the validation structure you´ll use it anywhere (Even in ASP.NET!).

Actual Features are:

1. A bunch o Validators :)
2. Ability to inject custom validation.
3. Properties Validation
4. Arguments Validation
5. Inherited Validation (validation on interfaces or base classes propagation)
6. Automatic Valitation with Windsor Integration

Check it out, at:
http://stormwind-svn.cvsdude.com/svn/Stormwind.ValEver/Trunk