Skip to content

No mention of TargetFramework Precedence/Resolution in Article #36845

Closed

Description

We've been trying to debug an issue where our net7.0-windows10.0.19041.0 app is picking up the net7.0 assemblies in our NuGet package instead of the proper OS specific net6.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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

📌 seQUESTeredIdentifies that an issue has been imported into Quest.Pri1High priority, do before Pri2 and Pri3doc-enhancementImprove the current content [org][type][category]dotnet/svcstandard-library/subsvc

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions