After a lot of digging (I had this issue for a long time before posting) I found the issue. One of the NuGet package sources in my list was down. If I remove that from the list, everything goes smoothly. With it in, it bogs down even if no packages in my packages.config are related … Read more
The reason that the NuGet package manager adds assembly binding redirects to library projects is because there are types of projects where the output type is a library, but there are special mechanisms in place to assure that the library’s app or web config file will be applied at runtime. This is opposed to more … Read more
For update all packages in all projects Nuget Package Manager GUI extension can do it with one click. How it works Open your project workspace in VSCode Open the Command Palette (Ctrl+Shift+P) Select > Nuget Package Manager GUI Click Load Package Versions Click Update All Packages
In our company we have solved the cascading updates problem with the following setup. First we have the following setup for our NuGet repositories and build server. There is an internal NuGet repository that holds all the published packages for the company. This repository is just a shared directory on one of our servers. Each … Read more
At the moment, NuGet doesn’t support installing packages resources elsewhere than the default location. There’s an existing NuGet work item that would cover this feature : #1914 – Allow package resource folders to be configurable.
.nupkg files are just ZIP files with some metadata, so you can have a look at the contents. The NuGet Package Explorer should make it a little easier to view the contents. The NuGet Gallery (e.g. https://www.nuget.org/) has a “Download” link on the right hand side, otherwise just install the package into an empty project … Read more
It’s a file that’s mostly a NuGet implementation detail, and should not be dealt with directly (it may go away or change in the future). But for reference, it contains a list of paths that point to all the packages.config in the solution. Typically there is one per project that uses NuGet.
The package source was offline !! I installed VS2017 professional on my system and opened an existing project and found that multiple packages were missing. I tried everything I could, without looking at Package Source !! I am writing this answer as I tried the below solutions but none of them worked : Clearing the … Read more
First, download the .nupkg file: Follow the instructions at How to download a Nuget package without nuget.exe or Visual Studio extension? Or use my Google Chrome extension NuTake Secondly, install the .nupkg file into your project Follow instructions at How to install a Nuget Package .nupkg file locally?
I’ve faced the problem several times, and all but one were solved by just closing and then restarting visual studio 2017. So if you’ve not, please try restarting VS, then if that fails, look for more serious solutions.