How to efficiently deal with Nuget packages version conflict in large solution.

• Maintain a common Folder will be used as the package source and all projects should use that common source as nuget package source.

• On the build server or developer machine the only source for the nuget packages will be this package source. We'll disable the other nuget sources on the server.

• So if by mistake anyone add the nuget package from nuget.org, it will be caught during build as build server won't find that version package on the build server.

• You can also manage the package at solution level. This will give you option to view the nuget version for the each of the project in the solution and then you can update them all at once to the latest version.

• http://blog.spinthemoose.com/2013/04/21/nuget-tip-3-manage-packages-at-the-solution-level/

• You can set local repository from the nuget package window in visual studio.

• http://stackoverflow.com/questions/26792624/how-to-enforce-same-nuget-package-version-across-multiple-c-sharp-projects

• http://www.hanselman.com/blog/HowToAccessNuGetWhenNuGetorgIsDownOrYoureOnAPlane.aspx