NuGet.Client | Client Tools for NuGet - including Visual Studio extensions | DevOps library

Here is a full method to download a nuget package and load it. It's just a POC - you'll want to configure it for your use case.

in your Visual Studio

I believe this is an example of an XY problem. NuGet is designed for packages to be immutable, so you're working against the design if you recreate the same package version with different content, even for testing. You only made a passing comment about automatic packaging and deploying, but didn't explain why you're writing custom code to download packages rather than using nuget.exe, so it's hard for me to make a good suggestion.

If you have a CI/CD environment where packages are created automatically, and other tests automatically use them, then I recommend the packages are built with prerelease version numbers and published to a dev nuget feed. For example, here you can see where the ASP.NET team's CI server publishes dev builds of a package, multiple per day. When they're ready to publish the production ready version, a different CI build packs without a prerelease version and pushes to nuget.org instead of their dev feed.

Depending on what you're trying to do, changing the global packages folder might work for you. Assuming you're using git for source control, if you make your test's global packages folder in an ignored part of your git repo, then git clean -Xdf will delete it, and I believe it's common for CI servers to clean before a build. This is also something I've done for local, manual testing where I didn't want to pollute my global cache. I just delete the folder once I'm done.

Ultimately the package cache is just a folder, which you can delete using System.IO APIs, no need for using NuGet APIs. Although, if you want to account for the fact that nuget.config files can change the global packages folder, you might want to use the NuGet APIs to find it. If you don't mind having all packages deleted, you could just run nuget.exe locals global-cache -clear and avoid writing any code.

How can I build the Nuget2 repo or is there maybe another way to tackle my problem with the Nuget.Server?

You also need download the solution NuGet.Client and unzip it to the folder NuGet.Client of your current solution.

When you download the solution NuGet2, you will find the folder NuGet.Client is empty. That is the reason why you got that error:

"error MSB3552: Resource file "....\NuGet.Client\src\NuGet.Core\NuGet.Frameworks\Strings.resx" cannot be found."

To resolve this error, please download the NuGet.Client solution and unzip it, copy all contents in the folder NuGet.Client-49234c230df0fc01868d8b90e667af89be8cc4f6 to the NuGet.Client folder, then build the project.

Hope this helps.

Yes! You need to consume the NuGet.Configuration package available at https://www.nuget.org/packages/NuGet.Configuration/4.6.2.

Then you can use the following code -

Found it! Must manually get it from nuget.org using VSLangProj150 Version 1.0.0 or as I did, I just added the following:

to my packages.config file and then let VS 2017 automatically restore any of my missing packages!