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.
Context: Using Unity in (C#) ASP.NET MVC3 framework.
Mark Seemann suggests “In ASP.NET MVC applications it’s global.asax and a custom IControllerFactory” – (Source).
I have read other credible sources suggest to use the UnityDependencyResolver (MSDN, Adam Tuliper, Darin Dimitrov).
Darin also suggests that the two are mutually exclusive.
Which way is best practice?
MVC 3 introduced a new way to handle Dependency Injection called IDependencyResolver. In MVC prior to MVC 3, you would use IControllerFactory. In MVC 3 you would use UnityDependencyResolver.
UnityDependencyResolver is an implementation of IDependencyResovler interface. This allows Unity to be integrated into .net without having to write a custom IControllerFactory.
They are mutually exclusive, in that if you use one you would not use the other.