I'm not a big fan of attribute-based validation because I find there are often complex requirements that involve asynchronous operations that often break the attribute model. I prefer more fluent validation using rules that can be shared between the client and server and can handle asynchronous scenarios. For those times when I do have to use a ...

Sometimes I love how a little reflection can work magic. In this case I was building what I'll call a ''non-intrusive'' validation system. The project contains entities that are generated by templates, and it would be extremely difficult to crack open those templates to put in a lot of custom validation code. So I decided to approach it using a ...

Line of business applications are full of what we call ''CRUD'' screens for Create, Read, Update, and Delete. Jounce addresses common concerns that are found in these types of transactions: Is Dirty and Commit It is common to check the status of a record and only apply changes when changes actually exist. Once a user edits a field, it is ...

Validation is a topic that comes up quite frequently. One concern is how to honor DRY (don't repeat yourself) principles and create a framework that is reusable across layers. There are some very robust and tested frameworks out there, but sometimes they might be more than what you are looking for. In this post, I'll show you how to build a ...