No mention of TargetFramework Precedence/Resolution in Article #36845
Labels
dotnet/svc
📌 seQUESTered
Identifies that an issue has been imported into Quest.
standard-library/subsvc
We've been trying to debug an issue where our
net7.0-windows10.0.19041.0
app is picking up thenet7.0
assemblies in our NuGet package instead of the proper OS specificnet6.0-windows10.0.19041.0
target we have in our package (for the Windows App SDK).Apparently, this is the expected behavior (from the decision made in the spec)!
Though this doesn't really make sense to us and doesn't appear to be documented in the TFM article here.
There are some useful tools for this apparently too: https://aka.ms/s2m3th
This seems to be a related issue: NuGet/Home#7416
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
Associated WorkItem - 189690
The text was updated successfully, but these errors were encountered: