From within VS 2022 I navigate to <Tools><NuGet Package Manager><Manage NuGet Packages for Solution...>
Then I select <Manage NuGet Packages for Solution...> but nothing happens. There is no error and no dialog is displayed. I mean, literally, absolutely nothing happens.
Has anyone seen this / know how to fix this?
OK I can see the Nuget Package Manager now.
Upon exiting VS 2022, the IDE prompted me . . - (Do you want to save your changes?) I had been clicking (No) - This time clicked (Yes) - The IDE pointed out the (.sln file) asking to overwrite the existing - I clicked (Yes) - then, After saving the new .sln file I am now able to see the UI for Nuget Package Manager
Related
Does anyone know how to install Autofac.Extensions.Hosting from a NuGet package within Visual Studio (2019)? I see the project here GitHub Autofac.Extensions.Hosting. Within the project instructions, it states that you can "reference the from NuGet". However, I can't find it within Visual Studio's NuGet Package Manager. Is it not available yet, or am I doing something wrong.
Thanks.
It was never published because it's basically just one extension method. The readme needs to be corrected. If you need the extension method, just copy paste it.
I've been using visual studio code as a second display (with visual studio as the first) to view/edit code mostly JavaScript since you can right click/format the code with easy.
But I recently took to time to study how it's c#/asp.net core debug functionality has evolved and it seems it has become even more easier to start whipping debug in no time.
But there is one thing I haven't figured out and whether it's even possible. That's it managing nuget packages. Visual studio offers a nice package manager ui to view installed packages and which packages might need a version bump.
It's there an alternative for visual studio code other than browsing the nuget site and checking which of your referenced packages have updated and editing the .csproj manually or running dotnet add <project> package ...?
This is probably not relevant anymore, but for anyone else also searching for something like this, there is a pretty handy extension for VSCode called Package Manager GUI here.
I have an ASP.NET MVC 4 application. I used NuGet to update all of the NuGet packages that were installed when I created the application. One of the packages was Microsoft.Bcl.Build.
After updating these, NuGet displayed the following message at the bottom of its window:
I have since restarted Visual Studio several times, but the message still exists. When I checked the installed packages, it did appear that the updated version (1.0.8) of the package was present.
How can I fix this?
Instead of deleting all of ~/packages, see if there are any *.deleteme files in ~/packages and delete them. Then restart Visual Studio.
I believe this problem is caused by the packages being read-only or otherwise inaccessible at the file system level.
Packages under source control
Temporary work-around (untested)
Check out the entire packages folder prior to telling NuGet to restart Visual Studio to delete the packages.
Permanent work-around
I found that this could be permanently resolved by removing the packages from source control and instead using NuGet Package Restore.
Packages not under source control
Temporary Work-Around
I worked around this by deleting from the solution's packages folder all of the files that referenced the package in question. Specifically, these were:
Folder: Microsoft.Bcl.Build.1.0.7
File: Microsoft.Bcl.Build.1.0.7.deleteme
In my case, the relevant package folders remained in ~\packages, although they were empty. I deleted the folders and restarted Visual Studio, and this warning went away.
I've just deleted the folders of each package that had error in the Packages folder in my solution folder and also deleted the .deleteme files and everything works fine!
1) Delete the entire ~\packagesfolder.
2) Restart VS.
3) Go to Manage NuGet Packages and Restore
I'll agree that this can happen when your packages folder is under source control. If you like to have it there, instead of removing the bindings you can check it all out, remove the package with the NuGet Package Manager, and then check in after wards.
In my experience, I found my answer on this thread, but using a combination of a couple of different answers above so I thought I would share what I found.
I had the exact same issue with "Microsoft.Bcl.Build" as the original poster. I had been trying to update references for other functionality using NuGet and had issues with some of the updates (compatibility then rollbacks). After this NuGet failure, I started getting this error.
I initially used the selected answer and Jedidja's answer and was able to get this to work, but it only partially solved my problem. It did fix the VS restart error, but it caused a downstream issue with TFS as I could no longer check in the project as it was expecting that "*.deleteme" file. This got me thinking, so I did some testing. When I restored the file from recycle bin, I started getting the restart error again.
Here is where I deviated from the posted answers and got my full resolution to my version of the problem.
When I checked into TFS this time, the project checked everything in (after I got the projects all updated using NuGet while the "*.deleteme" file was deleted). Once it checked everything in, I noticed that file was still pending check-in so I checked the solution in again and TFS accepted that file, but it was as a deletion....assuming it checked in the first time and then VS auto deleted it which required the second check-in. Anyway....after the last pending change check-in, the file was gone and VS no longer complained about needing to be restarted. I can't say for sure because the problem is gone, but I get the feeling if I had checked the code in before deleting the file in the first place it might have solved the problem without manual file manipulation.
** Hi, everybody.**
i resolve this problem this ways.
If you have source control run the vs as administrator ( it is important )
in the solution packages -> delete thing about packages.
sample -> i deleted all entity framework version folders.
restart the vs
open solution and solution right click -> manage nuget packages for this solution.
you will see restore button :) restore
that is all.
If you are using Entity Framework 6, then you can install the NuGet package "EntityFramework.SqlServerCompact".
This enabled me to use the standard ASP.NET Identity tooling that comes with the project templates for 2013 and MVC5.
My aim is to have package restore working on a build server so that I don't have to check in binaries. At the moment, I'm simply trying to get it to work on my own machine using Visual Studio.
Here's what I've done so far:
Followed the instructions here http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages, including both setting the Tools-Options flag and the environment variable (belt and braces)
Installed the NuGetEnablePackageRestore package as suggested here NuGet package restore consent without NuGet
Checked everything in (the .nuget solution folder and its contents), but not the binaries I want to reference, because that's the whole point of the exercise
Here's what I'm doing:
Check out solution
Verify that nunit.framework.dll and moq.dll are not present in the checked out solution
Build the solution
Visual Studio complains that Moq is missing. I search for the dlls in the solution directory and find that:
nunit.framework.dll is present in the appropriate bin folders
Moq.dll is nowhere to be found
But there's more. This is truly mysterious, but if I do a fresh checkout, disconnect from the internet and build, I get precisely the same results - nunit.framework.dll is there, but moq.dll is not. The build process has conjured nunit.framework.dll literally from nowhere.
So it's something of an understatement to say that I am completely baffled. Can anyone suggest answers to the following questions:
Why is package restore not downloading Moq?
Where on earth is the build process getting nunit.framework.dll, if not the internet?
In vs, Options, Package Manager... there's a section "Package Cache", if you click on the "Browse" button it will take you to the location of the nuget cache in your machine.
Okay, I noticed in the documentation that enabling package restore was supposed to modify project files in order to add a new target. My project files did not have this change. Right-clicking the solution title in VS and selecting 'Manage NuGet packages...' then added the required changes and everything built as it should.
I checked, and package restore still appears to work when I have no internet access, so I'm still mystified about that. Does NuGet maintain some kind of cache of binaries outside the solution?
I am running VS2010 Ultimate, I used to have VS Web Dev 2010 Express with Nuget before: I uninstalled it before installing Ultimate.
In admin mode I uninstalled Nuget 1.5 from vs, restarted vs in admin mode, installed 1.6, and then restarted vs. Nuget worked for several days.
The next day, the package manager wont come up - it doesnt give me an error, it just wont load. If I try to uninstall it, the uninstall button is greyed out (which I assume means that the addin is in use). If I restart vs, then I can uninstall.
I have tried uninstalling Nuget and reinstalling it several times (no error messages generated)
Trying to load Package Manager Console and the Package Manager Settings, dont launch anything.
Is there a way to install version 1.5? I've looked for a link but cannot find one.
Is there a log file I can check to see what is wrong?
This has been an extremely frustrating issue for me.
Update:
I used devenv /log, tried to open the package console.
Here's part of the log file:
225 Leaving function LoadDTETypeLib VisualStudio 2011/12/30 21:54:45.181
226 ERROR SetSite failed for package [NuGet.Tools.NuGetPackage, NuGet.Tools, Version=1.6.21215.9133, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a] {5FCC8577-4FEB-4D04-AD72-D6C629B083CC} 80131509 VisualStudio 2011/12/30 21:54:45.196
227 ERROR End package load [NuGet.Tools.NuGetPackage, NuGet.Tools, Version=1.6.21215.9133, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a] {5FCC8577-4FEB-4D04-AD72-D6C629B083CC} 80131509 VisualStudio 2011/12/30 21:54:45.227
228 Warning Package failed to load; error message suppressed by skip flag {5FCC8577-4FEB-4D04-AD72-D6C629B083CC} VisualStudio 2011/12/30 21:54:49.486
229 Entering function CVsPackageInfo::HrInstantiatePackage
Thanks!
Finally got it working: had to delete c:\User Data\\AppData\Roaming\NuGet\NuGet.Config (which was empty) and now it can load.
I had the same problem, nuget worked yesterday but not today with "SetSite failed for package [NuGet.Tools.NuGetPackage" in the VS log.
After a lot of trying and failing I found this page, and then the discussion at http://nuget.codeplex.com/discussions/284604
I followed the advice from bsparkinson there :
Unistalled Nuget.
Searched for nuget in %appdata% and deleted everything
Reinstalled Nuget.
And now it works.
You mentioned:
If I try to uninstall it, the uninstall button is greyed out (which I
assume means that the addin is in use).
Is it greyed out even when you run VS as an admin? The button should only be greyed out if you're not running as admin.
The other thing you should do is try running the following command. You'll need to use the devenv command prompt.
vsixinstaller.exe /uninstall:NuPackToolsVsix.Microsoft.67e54e40-0ae3-42c5-a949-fddf5739e7a5
That should uninstall the NuGet VSIX. After doing that, the following directory should be gone or empty: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\\