I’ve added some libraries to a VS 2010 solution using Nuget (RestSharp, Twilio, etc.). When I pull the same solution down to a new PC from TFS and try to build it, all the references to those assemblies are broken (error “namespace cannot be found…”). Is it necessary for each developer who works on this VS solution for the first time to independently install the same Nuget packages on their PCs?
Thanks,
Jim
I’ve added some libraries to a VS 2010 solution using Nuget (RestSharp, Twilio, etc.).
Share
No, but you need to be sure the assemblies are all included in the same relative path so Visual Studio can find them. You can include the solution’s nuget packages directories, which is where I think it stores a copy of the libraries to be referenced by the project(s).
Incidentally, including said diretories may be effectively the same as “installing the packages”. If you include all the files that NuGet uses in its management of packages, NuGet will behave the same as if you had installed them. But you don’t need to do the actual package install via NuGet for it to work… or even have NuGet installed in Visual Studio in the first place. It’s just a matter of the proper files being where the Visual Studio project files expect them to be.