There might have been a situation when some package reference in your project are not found when you copy it to a different machine.
To solve this, we generally add referenced libraries into source control.
Should we do the same with packages and add them to source control? The answer, No. Including binaries can grow the repository size like crazy over time, making cloning more and more painful. NuGet 2.0 solves all of these issues for you in a simple manner.
If you have a solution that is either already using NuGet packages, and then all you have to do is right click on the Solution node in Solution Explorer and select Enable NuGet Package Restore.
This will download any resource that is missing into the packages folder every time the project is complied.
- Using NuGet without committing packages to source control
- NuGet 2.0 (.NET Package Manager) released – GO UPGRADE NOW and here’s why (hanselman.com)