Lots of bugs encountered while upgrading nuget from v2 to v4 #7472
Labels
Functionality:SDK
The NuGet client packages published to nuget.org
Priority:3
Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
Triage:NeedsMoreInfo
We are running into problems with the new way packages are structured. Nuget v2 is not able to handle this. This is why we want to update our nuget from v2 to v4. However we are running into some serious problems with the nuget libraries:
FolderNuGetProject
simply returns a empty IEnumerable when you callGetInstalledPackagesAsync
. This looks like a pretty serious bug to me.PackagesConfigNuGetProject
but that one does not install any packages? It just updates a packages.config file.async await
which means we have to wrap everything up in another class.Iam getting the feeling the v4 library is not designed or meant to be consumed by 3th parties. It seems that its only meant to be used in VS and msbuild. Am I correct in this?
If the above is true what is the best way to add support for the new package structure which nuget v2 cannot handle? Do we have to build our own client using the REST api?
The text was updated successfully, but these errors were encountered: