Closed ilexp closed 5 years ago
feature/package-framework-selection
branch.master
release
Related: Issue #696
Hmm I was under the impression we needed to upgrade nuget in order to support targetframework folders but it seems you have a solution that can do this without upgrading nuget? Nice work!
Hmm I was under the impression we needed to upgrade nuget in order to support targetframework folders but it seems you have a solution that can do this without upgrading nuget? Nice work!
Limited support only, so you're correct when thinking about the full deal.
What we get is an explicit priority decision between "old" frameworks such as .NET Framework or PCLs profiles, as well as explicit handling of per-framework files within a package. However, new frameworks such as .NET Standard will only show up as "Unsupported, Version 0.0" and while it would be possible to do custom parsing of the lib folder to distinguish them, a NuGet upgrade would solve this properly.
Usually, a .NET Standard library would still be consumable, since as far as I recall the official recommendation is to multi-target most of them with both .NET Standard and the equivalent .NET Framework.
master
release
Merged and released.
Summary
The current PackageManager implementation does not explicitly handle NuGet target framework folders, causing some packages to fail installation in Duality. The PackageManager should be extended to have a clear framework and version preference, leading to more reliable and predictable results for those packages.
How to reproduce
Workaround
net40
or lower target framework folder.Analysis