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.
When the .net 2.0 framework first came out, the provider model was all the rage. 2.0 even shipped with a bunch of default providers (Membership, sitemap, role). Since the release of 2.0, the hype has died down, and whilst I still use providers day to day, it seems to get far less press.
I was wondering if this is because people are using something other than providers and they’ve been superseded, or is it simply because the take up wasn’t as big as other IoC methods?
It actually hasn’t died down. DI is still big. There are many DI frameworks out there to choose from. Yes, it’s not hard-baked into every part framework like it should absolutely be, but its still a very good practice to follow. For instance, I was using the P&P’s custom application blocks to do DI. Until they ditched it for Unity. Now I’m using unity.
A lightweight DI framework is a good idea for any large extensible application.