For anybody stumbling across this, now there is the following option : Right-click your solution > Manage NuGet Packages for Solution… … Or: Tools > Library Package Manager > Manage NuGet Packages for Solution… And if you go to the Installed packages area you can ‘Manage’ a single package across every project in the solution.
Setting an execution policy to RemoteSigned or Unrestricted should work. It must be changed under an administrator mode via a PowerShell console. Be aware that changes will be applied according to the bit version of the PowerShell console, so 32bit or 64 bit. So if you want to install a package in Visual Studio (32 … Read more
ReSharper 2016.1 has a feature to remove unused NuGet. It can be run on a solution and on each project in a solution and it does the following things: Analyze your code and collecting references to assemblies. Build NuGet usage graph based on usages of assemblies. Packages without content files, unused itself and without used … Read more
How to resolve Nuget Package Version and Path in Pre-Build Event of a Project? If you want to reinstall package automatically in Pre-build event, I am afraid you can`t achieve it currently. We could use the command Update-Package -Id <package_name> –reinstall to reinstall the packages to your project in the Package Manager Console, but it … Read more
I wrote Steve from the TPL dataflow team about this problem and he responded me with the following download link: http://download.microsoft.com/download/F/9/6/F967673D-58D6-4E3F-8CA9-11769A0A63B1/TPLDataflow.msi This is a CTP version, but the date matches the Nuget package with version number 4.0, so I think it’s the latest version that was compiled against .NET 4.0.
Referencing .NET Standard 2.0 packages is supported using the following: NuGet 3.6.0 or higher for VS 2015 (from NuGet’s download site – may not yet be listed as recommended latest) Install the “.NET Standard Support for Visual Studio 2015” from https://aka.ms/netstandard-build-support-netfx (NuGet in VS will also print a link to this in its output window). … Read more
This answer builds upon the principles used to package libraries targeting the .NET Framework. Read the linked answer first to better understand the following. To publish the portable .NET library, you will need to create a NuGet package with the following structure: \—lib \—dotnet MyPortableLibrary.dll MyPortableLibrary.pdb MyPortableLibrary.XML All three files will come from your project’s … Read more
You could try constraining the package so it your project will only allow a particular version to be used. Then all updates to any newer version will be prevented. You can do this by editing your project’s package.config file. For example, the line below should only allow version 2.1.0 to be used. <package id=”SomePackage” version=”2.1.0″ … Read more
As of 2020 there is no officially supported way to do this. However various people have come up with ways to achieve it, and the current best way is to install a NuGet package prepared by the amazing Teroneko. Then all you need to do is edit your .csproj to update all your project to … Read more
This is a known issue with nuget version 3.4, which is included with Visual Studio 2015 Update 2: The NuGet.config file in your %AppData%\NuGet\ folder has accidentally been emptied. To fix this: Close Visual Studio 2015, delete the NuGet.config file in the %AppData%\NuGet\ folder and restart Visual Studio. A new NuGet.Config file will be generated … Read more