What are all these packages? [closed]

M

mike.rose

New Member
\[quote\] Possible Duplicate:
Why does ASP.NET MVC 4 have so many NuGet packages and which are truly important? \[/quote\]When I create a new ASP.NET MVC 4 Intranet Application, the resulting project has an astounding twenty NuGet packages:
  • EntityFramework
  • jQuery
  • jQuery UI (Combined Library)
  • jQuery Validation
  • Json.NET
  • knockoutjs
  • Microsoft .NET Framework 4 HTTP Client Libraries
  • Microsoft ASP.NET MVC 4
  • Microsoft ASP.NET Razor 2
  • Microsoft ASP.NET Web API Client Libraries
  • Microsoft ASP.NET Web API Core Libraries
  • Microsoft ASP.NET Web API Web Host
  • Microsoft ASP.NET Web API
  • Microsoft ASP.NET Web Optimization Framework
  • Microsoft ASP.NET Web Pages 2
  • Microsoft jQuery Unobtrusive Ajax
  • Microsoft jQuery Unobtrusive Validation
  • Microsoft.Web.Infrastructure
  • Modernizr
  • WebGrease
I understand that this stems from Microsoft's "One ASP.NET" vision, where there's not a strict separation between ASP.NET and ASP.NET MVC apps; you just add the packages you want. But the result seems to be package overload.Which of these packages do I need, and which can I do without?For instance, it seems obvious that knockoutjs is optional, whereas removing Microsoft ASP.NET MVC 4 will break my MVC app. Can someone categorize all twenty of these into "you need this for MVC" or "you only need this if you're doing special feature XYZ"?
 
You must log in or register to reply here.
Back
Top