Its never to late, recently I am seeing people around me who are misunderstanding NuGet Package Manager in Visual studio. Shouting Stop adding NuGet packages / library to source control First version of NuGet was release in January 13, 2011¬†and lots of things are changed since then. One of my favorite feature of NuGet is package restore. This particular feature is available since Version 1.6 release on 13th December, 2011. It helps to avoid adding source control memory consuming package files and folders and reduce over all size of my clean solution folder. Let me start with an example. I created a demo MVC 4 Internet Application, once created I went into NuGet package manager at solution level and updated all the packages installed by default in the MVC4 project template. After running the update, size of the packages folder in the solution folder was approximately 100 MB. This » Read more

 Jsinh        

One thing any .NET developer is addicted to is Nuget Package Manger. Life has become so easy, no more hassle of maintain all those 3rd party libraries or remember them or list them down in some document. No more Reference DLL not found errors to deal with and all credits goes to Nuget. Nuget handles it all for you and gets whatever is needed from Nuget Server on demand or as configured. I am writing this one specifically cause there are situations when you might not be having internet access or Nuget.org went under maintenance or you are in some remote area on earth (or other planet) or in a plane or internet access is prohibited in your organization (as in my case on my office Developer VM pffff) Every time you add a package from NuGet or using NuGet package manger, it create a cache copy of that » Read more

 Jsinh