Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
.NET’s ProviderBase was established in the 2.0 release of the .NET Framework. Have there been any new features since then that supercede or improve on this pattern that should be used as an alternative?
The provider pattern definitely had its day, but these days dependency injection frameworks have become so powerful and easy to use that they are a better option.
Drawbacks I discovered when using the provider pattern:
found it really tedious to write the code for the neccessary configuration classes.
had to manage alot of painful and redundant configuration.
discovered that you must limit your inheritance class to ProviderBase.
If you need to stick with Microsoft stuff, then Unity can work. There are plenty of others DI frameworks such as Structuremap or Ninject that have a much more simple way of hooking up dependencies.