Fix compatibility task paths in props and targets #22318
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the repository tfm was updated to net7.0 on: 45710fb, the wrong compatibility task path was updated to use net7.0 as the directory containing the task. The one that was updated is the one that ships as part of the OOB package and the package intentionally targets net6.0 so that we can run this task on a 6.0 SDK even if a newer package is used.
The one that needed to move to net7.0 is the one declared when using the SDK built-in tooling as the SDK now generates a layout for net7.0.
Discovered on: dotnet/runtime#60847