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
Dependency groups are selected independently, there are no changes for walking the graph
If any assets are available within a package including non-TFM specific assets then no fallback is done
If zero assets are available and the package would be considered incompatible, then and only then fallback to trying with PackageTargetFallback to select assets
Compatible assets are determined by what the project is going to select, other folders such as content/ and tools/ are ignored
This needs investigation to see if existing packages on the gallery would be broken. And also if this behavior would even fix all packages in a real solution when using a fall back of net461
anangaur
changed the title
Soft framework fallback for PackageTargetFallback
Enable .NET Core 2.0 projects to work with .NET Framework 4.6.1 compatible packages
Jun 1, 2017
AssetTargetFallback allows falling back to another project framework only if no compatible assets are found in the package.
FixesNuGet/Home#5192FixesNuGet/Home#5268
emgarten
added a commit
to NuGet/NuGet.Client
that referenced
this issue
Jun 2, 2017
AssetTargetFallback allows falling back to another project framework only if no compatible assets are found in the package.
FixesNuGet/Home#5192FixesNuGet/Home#5268
This needs investigation to see if existing packages on the gallery would be broken. And also if this behavior would even fix all packages in a real solution when using a fall back of net461
[anangaur] Spec: https://github.com/NuGet/Home/wiki/Enable-.NET-Core-2.0-projects-to-work-with-.NET-Framework-4.6.1-compatible-packages
The text was updated successfully, but these errors were encountered: