You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
unable to publish/list the packages in Nuget Package Explorer for the latest version of New Nuget server version 3.0.1.0
FY!, this a plain nuget server using to host the packages, created using the approach creating a empty asp.net web application and then installed the nuget server in that solution using manage nuget package sources and then host the applciation on IIS.
We are able to list the packages using the nuget.exe and VS but not with the Nuget package explorer.
Nuget package explorer is working with the previous version of Nuget server after upgrading to the latest version it stopped working
The root cause is that $select does not work on NuGet.Server 3.x. This is not impacting the official NuGet client (since it does not use projection) but is affecting other clients, like NuGet Package Explorer (NuGetPackageExplorer/NuGetPackageExplorer#275).
@cmreddyv commented on Thu Dec 14 2017
unable to publish/list the packages in Nuget Package Explorer for the latest version of New Nuget server version 3.0.1.0
FY!, this a plain nuget server using to host the packages, created using the approach creating a empty asp.net web application and then installed the nuget server in that solution using manage nuget package sources and then host the applciation on IIS.
We are able to list the packages using the nuget.exe and VS but not with the Nuget package explorer.
Nuget package explorer is working with the previous version of Nuget server after upgrading to the latest version it stopped working
Can find the details at NuGetPackageExplorer/NuGetPackageExplorer#275 (comment)
@emgarten commented on Thu Dec 14 2017
@joelverhagen any ideas why this would have changed on NuGet.Server?
NPE is using very old 2.x NuGet libraries.
@joelverhagen commented on Fri Dec 15 2017
Moving to NuGetGallery repository, as this is a server-side issue.
The text was updated successfully, but these errors were encountered: