I liked the Application blocks of then, for their simpler design.
- Interdependencies between application blocks
- Ease of understanding
I still don’t know if i am going to use the Enterprise Library Monster (as it is today). I would have definitely used it a couple of years back.
Prakash is talking about the "Provider Pattern" – One of the most interesting features in ASP.NET 2.0
The pattern itself is exceedingly simple and is given the name "provider" since it provides the functionality for an API. Defined, a provider is simply a contract between an API and the Business Logic/Data Abstraction Layer. The provider is the implementation of the API separate from the API itself. For example, the new Whidbey Membership feature has a static method called Membership.ValidateUser(). The Membership class itself contains no business logic; instead it simply forwards this call to the configured provider. It is the responsibility of the provider class to contain the implementation for that method, calling whatever Business Logic Layer (BLL) or Data Access Layer (DAL) is necessary.