Hello,I have recently installed VS2015 Enterprise edition and I have noticed a strange behavior with NuGet manager on VS2015.Basically, it works perfectly fine if I launch the dialog from the Tools menu (Extensions and Updates). However, if I right click on a project name, in the solution explorer and select 'Manage NuGet Packages' then a new tab opens up but NuGet generates anerror 'failed to retrieve metadata from srouce.' .here is the weird part: if I try the same thing using the NuGet PM console (Tools - Nuget - PM console), then everything works fine and I get no errors. I can install whatever i want.
Packages are installed into a Visual Studio for Mac project using the NuGet Package Manager. NET project, provided that the package supports the same target framework as the project. Open the Program.cs file (located in the Solution Pad) and replace the file contents with. There are no open issues.
Also, I have VS2013 ultimate installed on the same PC, and I experienceno issues whatsoever from within VS2013. So this issue seems to be VS2015 specific.
The NuGet package version i have installed is 3.1.60724.766can anyone please explain to me why the NuGet Package manager dialog for projects fails to retrieve the metadata, but the global extension manager or the PM console work fine.few facts: I know my organization does not have a proxy server, but they do use a strict firewall. Is it possible that the dialog uses a different port than the console?Thank you. Ok I did that, but I've found what looks like a work around.
This is copied from a StackOverflow post:I had the same issue, and after struggling for a couple of hours I finally got it.There seems to be an issue with the later version of nuget source at urlTo fix the issue.go to Tools - NuGet Package Manager - Package Manager Settings, under Package Sources create a new package source Name: NugetSource Source:Move the newly created source to the top of the list under Available package sources. Click OK and restart Visual Studio.It worked like a charm for VS2015.StackOverflow post: https://stackoverflow.com/questions/28288328/nuget-the-remote-server-returned-an-error-504-gateway-timeout/2830431. Hi rob8861,If I right click on a project name, in the solution explorer and select 'Manage NuGet Packages' then a new tab opens up but NuGet generates an error 'failed to retrieve metadata from srouce.' .Whether all projects have the same issue? For example, create a simple WinForm/C#Console app, and then right click it in solution explorer windows-Manage NuGet Packages, how about the result?Since this forum is to discuss the VS IDE usage, to make sure that whether it is related to the project itself or the VS IDE, how about testing it in other VS2015 machine using the same project?If you don't have other VS2015 Environment, maybe you could share me a simple sample with one drive, I will test it in my side.But if all projects have the same issue, maybe the right click items met a loaded issue. If possible, please repair your VS from the control panel, and then re-create a new project, test it again.Best Regards,JackWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.Click to participate the survey. Hi Jack,I am getting the error message on every c# project.I tried installing the same VS2015 on a different laptop which is connected to a different network, and I do not experience this issue. Everything worked fine.I tried repairing VS2015 but the issue stills exists. I even tried removing and then reinstalling NuGet Package manager, but that did not resolve the issue either.my company blocks all type of file sharing including onedrive, dropbox, googledrive etc.I am starting to think this might be an internal network issue, but why would it work using the console but not using the gui dialog. If the firewall blocked something, shouldn't it be blocking it from the console as well?if I create a new project and right click - Manage Nuget Package, I get the error message. But If I open the PM console and type Install-Package then I get no error and the package gets installed. That's what is driving me crazy.Can you please find out why this is happening?
Are there different ports being used for both?Thanks. Hi rob8861,'failed to retrieve metadata from srouce.'
.Could you share us the detailed error message? Maybe you could share me a screen shot about it.(1)If the same setup file worked well in other machines, at least, we could know that it is not the setup file issue.(2) Did you get any error when you install the VS2015? If not, I'm afraid that it is not the VS IDE setup issue.(3) To make sure that it is not the add-ins or extension tools' issue. Please run your VS in safe mode:(4) Run your VS as the admin. am starting to think this might be an internal network issue.I'm not very sure that whether it is related to your network, maybe you could use the same network as other machines in your machine, test it again. If it worked well, at least, we could know that it is not the VS IDE issue, and then you coulddiscuss this issue with your IT, maybe it has certain limitation in your specific network.Best Regards,JackWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey.
Hi Rob,the NuGet package version i have installed is 3.1.60724.766.Where did you download this version? I check it in my default VS2015, it is the 3.0 version.Maybe you could share me the download link, I will download and install it in my side.Like my previous reply:I'm not very sure that whether it is related to your network, maybe you could use the same network as other machines in your machine, test it again.Could you check that whether it is related to the network in your side?Best Regards,JackWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey. Hi rob8861,Thanks for your friendly response.It seems that I didn't update it to the latest version in my side. But after I update it to the 3.1.60724.766 version, it still works well in my side.Please check that whether it has some limitations in your local internet for the package sources in the following link.Best Regards,JackWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey. Hi Matt,If this is a local internet issue, are there any suggestions on what I can do to to prove it and resolve it?I'm afraid that I have no directly answer for it, one idea is that you could discss this issue with the IT of your team, or you could change the internet without using the local type, test it again.
At least, it is the way we could narrow down thisissue.Please also add these site as the trust site in your IE settings, test it agian.Thanks,JackWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey. Hi j.pv,Since different members got the same issue, t o get the issue confirmed and diagnose by product team, would you please createconnect report for it?
You will get email notification for update.Maybe we could get better response from the product team members directly.Thanks,JackWe are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.Click to participate the survey. Ok I did that, but I've found what looks like a work around. This is copied from a StackOverflow post:I had the same issue, and after struggling for a couple of hours I finally got it.There seems to be an issue with the later version of nuget source at urlTo fix the issue.go to Tools - NuGet Package Manager - Package Manager Settings, under Package Sources create a new package source Name: NugetSource Source:Move the newly created source to the top of the list under Available package sources. Click OK and restart Visual Studio.It worked like a charm for VS2015.StackOverflow post: https://stackoverflow.com/questions/28288328/nuget-the-remote-server-returned-an-error-504-gateway-timeout/2830431.
I seem to have exactly the same issue, however, in the Package Manager Console -. Install-Package works fine. Get-Package -ListAvailable fails with the same error as the UI package manager ('Failed to retrieve metadata from source.' )I presume the UI package manager's initial step (listing available packages) is equivalent to Get-Package, so this seems to suggest a general issue with searching for packages rather than installing packages.Jack-Zhai's workaround does allow me to list available packages through the UI package manager.
The Visual Studio 2017 15.3 NuGet client has been updated to support the new.NET Core 2.0 and.NET Standard 2.0 releases announced by Microsoft this week.NET Core 2.0 is a major of the company's modularized, open source, cross-platform implementation of.NET, based on a vastly expanded set of.NET APIs that have been standardized under.NET Standard 2.0, which dictates the API set required to be available in all.NET implementations.However,.NET Core. 2.0 and.NET Standard 2.0 functionality would be limited if they didn't play nicely with NuGet, the Visual Studio package manager that provides access to hundreds of thousands of third-party packages.Shortly after Microsoft's announcement, NuGet, under the.NET Foundation umbrella, announced support for.NET Core. 2.0 and.NET Standard 2.0 in the new for the Visual Studio.'
We are happy to announce an update to the NuGet client that comes bundled with Visual Studio 2017 version 15.3 RTW and.NET Core 2.0 SDK,' NuGet said in a Tuesday. 'This release introduces support for new scenarios such as.NET Core 2.0/.NET Standard 2.0, some new features, a series of bug fixes and performance improvements.' Microsoft earlier pointed out that a May found some 70 percent of NuGet packages (which manages more than 87,000 unique packages and more than 960,000 package versions) were compatible with.NET Standard 2.0.However, the company: 'The vast majority of NuGet packages are currently still targeting.NET Framework. Many projects are currently blocked from moving to.NET Standard because not all their dependencies are targeting.NET Standard yet. That's why we added a compatibility mode that allows.NET Standard projects to depend on.NET Framework libraries as if they were compiled for.NET Standard.'