Package Manager Overload
With the release of .NET Core and the related tooling for Visual Studio 2015, there are now three different package managers that can be used: NuGet, npm & Bower. At first going from 1 to 3 package managers may seem like overkill, and also completely unnecessary since before NuGet we didn’t use a single package manager at all and still seemed to get by.
NuGet is an open source package manager for Microsoft technologies(mainly .NET). It comes installed with Visual Studio and is even what Microsoft uses to redistribute it’s .NET CORE assemblies.
In the past for the .NET development community if you need a third party library, you use NuGet. Front-End? Use NUGET! Back-End? Use NUGET!
When to use each?
Here are some common uses for the three package managers in the new ecosystem.
- Entity Framework