CODEWITHSUNDEEP
visual-studio-2017nuget.net-standard-2.0
to StackOverflow
to StackOverflow

Reputation: 124696

Visual Studio 2017: how to include NuGet packages in solution folder

To date, using Visual Studio 2015, NuGet packagas are restored into a solution-specific "packages" folder, which I check in to source control. Our TFS Build server does not have Internet access, so it needs these local copies to successfully build.

I am now trying out Visual Studio 2017, with a .NETStandard Class library, and it no longer makes a local copy of NuGet packages - instead they appear to be stored in %HOMEDRIVE%%HOMEPATH%.nuget\packages. This means they are no longer available on the Build server.

How can I get NuGet to store packages locally?

Upvotes: 3

Views: 2038

Answers (1)

Matt Ward
Matt Ward

Reputation: 47907

You should be able to define a RestorePackagesPath property in your .NET Standard (SDK style) project which defines where the NuGet packages should be restored to.

You can use this to tell NuGet to not use the .nuget\packages directory but instead use some other directory relative to your project.

<PropertyGroup>
  <RestorePackagesPath>..\path\to\MyPackages</RestorePackagesPath>
</PropertyGroup>

Looking at the NuGet documentation they mention three possible approaches when using a project that uses PackageReferences.

  1. Set the NUGET_PACKAGES environment variable to a different folder.
  2. Create a NuGet.Config file that sets globalPackagesFolder to a different folder.
  3. Specify a different folder with the RestorePackagesPath MSBuild property.

Upvotes: 6

Related Questions