Per project: References->Nuget dictates what packages are referenced and restored. But, as Eastrall mentioned, the packages folder is now global and located in your user folder: C:\Users\[YourUsername]\.nuget\packages
As SayusiAndo guessed, the credentials were stored in Control Panel -> Credential Manager. After removing of which everything works fine. UPDATE: Two gotchas (as @Jurri mentioned in the comments): There may be two credentials to delete (Windows and Generic). The generic one, in my case, had “VSCredentials_” prefix. Restart VS.
I would suggest updating .nuget\nuget.exe with this command from the command line: nuget.exe update -self [EDIT] : Close VS Solution first. If there’s an update and the solution is opened, nuget.exe will be removed from the solution. You could automatically update nuget.exe on restore by modifying the .nuget\nuget.targets to add the above command. I’d look … Read more
NuGet is designed to allow you to easily add code libraries to your project. Things like JSON.NET, Entity Framework, etc. Chocolatey is actually built on top of the NuGet package system, but it is designed to fill a different need. Chocolatey wraps up applications and other executables and makes it easy to install them on … Read more
In the past, we’ve given developers the recommendation to not reference the meta package (NETStandard.Library) from NuGet packages but instead reference individual packages, like System.Runtime and System.Collections. The rationale was that we thought of the meta package as a shorthand for a bunch of packages that were the actual atomic building blocks of the .NET … Read more
You can solve it like this: NuGet.exe pack Foo.csproj -Prop Configuration=Release (reference)
NuPKG files are just zip files, so anything that can process a zip file should be able to process a nupkg file, i.e, 7zip.
Using the Copy target in the targets file to copy required libraries won’t copy those files to other projects which reference the project, resulting in a DllNotFoundException. This can be done with a much simpler targets file though, using a None element, as MSBuild will copy all None files to referencing projects. <Project xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″> <ItemGroup> … Read more
I have a similar situation with external and internal package sources with projects referenced in more than one solution. I just got this working with one of our code bases today and it seems to be working with the developer workstations and our build server. The below process has this scenario in mind (although it … Read more
I’ve found a workaround for this. Enable package restore and automatic checking (Options / Package Manager / General) Delete entire contents of the packages folder (to Recycle Bin if you’re nervous!) Manage Nuget Packages For Solution Click the restore button. NuGet will restore only the packages used in your solution. You end up with a … Read more