Many times, we want a certain set of validation to fire for some user and certain set of validation to fire for some other user. In this section, we will see how we can achieve the same using Microsoft enterprise validation blocks.
I have been writing and recording videos on architecture, design patterns, UML, enterprise blocks etc. You can view all my videos here. If you have any feedback, do email me at email@example.com.
- Validation application blocks: This article explains the 16 steps you need to perform to do validations using VAB.
- Client side validation: One of the shortcomings in VAB is that it does only server side validations. This article talks how we can leverage VAB for client side.
- Policy Application blocks: This article talks about how to implement plug and play mechanism using Policy application blocks.
- Logging application block: This article explains the 5 basic steps of how to use logging application blocks.
- Data application: This article talks about the four steps you need to implement data application blocks.
- Exception application block: This application talks about how we can use exception application blocks to log exception from project.
- Unity application block: This application talks about Unity Application Block in DI and IOC.
- UIP block: This article talks about Reusable Navigation and workflow for both Windows and Web using Microsoft UIP blocks.
There are times when you want validation according to the logged in user or customer. For instance, in the below figure, you can see we want different validations for both users. For one user, we want that the customer code should be minimum 2 characters while for the other user, we want it to be 5 characters.
Figure: Logged in user
Enterprise library helps us to solve this problem like a charm. To understand this article, you need to once read the basics of how to implement validation using VAB (validation application blocks). In case you are not aware of the basics, you can read the same from my previous article here.
To fire validation according to logged in user is a two step process.
First you need to define two different rule sets according to customer. For instance, in the below figure, you can see that we have defined two validations. The first validation checks if the customer code is minimum two length while the second validation checks if the customer code is five length.
In step 2, we just need to call the validation according to the user logged in using the “
static class. The
validate function of the
validation static class has two parameters, one is the customer object and the other is the rule name. So depending on logged in customer, you can fire the rules on the fly.
- Updated with links of Other Application Blocks