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.
I’ve an ASP.NET MVC application which I’ve upgraded from 2.0 to 3.0 in the past and now I want to upgrade it to 4.0.
I’ve tried to create a new ASP.NET MVC 4 project in VS2012 and it seems that ASP.NET MVC itself is now a NuGet package.
Should I reference it in form NuGet package like in the new project templates or just reference like 2.0 and pre 3.0 tool update (separate assemblies)?
My servers have ASP.NET MVC 4 installed so having MVC dll’s in /Bin seems to be a waste of space.
NuGetnowadays is the way to go. If you are still dealing with assemblies manually, I fear you’re doing it wrong.You definitely should install it through a
NuGetpackage. This will allow you no headaches when new updates appear. NuGet knows how to manage package dependencies correctly, that is, it’ll also update all other packages you have installed in your project to make them compatible with the latestASP.NET MVC. Things are really EVOLVING for the better in this specific case! 🙂