Geek Answers Handbook

Should I reference ASP.NET MVC as a NuGet package?

I have an ASP.NET MVC application that I upgraded from 2.0 to 3.0 in the past, and now I want to upgrade it to 4.0.

I 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 refer to it as a NuGet package, as in new project templates, or just refer as 2.0 and up to 3.0 tool updates (separate assemblies)?

My servers have ASP.NET MVC 4 installed, so having MVC-dll in / Bin seems like a waste of space.

+4
source share
1 answer

NuGet is currently the way to go. If you are still dealing with builds manually, I am afraid that you are doing it wrong.

You must install it through the NuGet package. This will not give you a headache when new updates appear. NuGet knows how to properly manage package dependencies, meaning it will also update all other packages that you installed in your project to make them compatible with the latest ASP.NET MVC . Things are really EVOLVING for the better in this particular case! :)

+5
source

More articles:


All Articles