I think NuGet is among one of the best things to come out of the .net open source community. NuGet has seen quite a significant growth in the past couple of years as more and more projects are added to the repository. Add to this the ease of VS Package Manager and you have a streamlined developer experience inside VS. As an indi-developer one might not face that much issues with NuGet packages in a solution because he/she is the only one sharing the code and the fact that all packages reside inside the 'packages' directory of the solution. Even if one is using source control then there is no need for adding binary packages into the repository. This will change if you are working as part of a developer team. I had been recently involved in a project with a reasonable team size but the potential of growing as the project progresses. The project is being built using ASP.NET MVC 4 with a handful of NuGet packages. Since the project is open sourced there is high possibility more contributors will end up cloning and/or forking the project.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

ASP.NET MVC,DVCS,NuGet,Visual Studio