-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve P2P handling for cross-targeting #1621
Conversation
1. Deal with UWP case where NugetTargetMoniker is needed instead of TargetFrameworkMoniker 2. Provide mechanism to override the moniker that is passed to reference 3. Provide mechanism to pick any target framework of reference 4. Provide mechanism to skip the best TFM computation for known single-targeting case
than one framework. | ||
--> | ||
<ItemGroup> | ||
<_MSBuildProjectReferenceExistent Condition="'%(_MSBuildProjectReferenceExistent.SkipGetTargetFrameworkProperties)' == '' and '%(Extension)' == '.vcxproj'"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be or
vcxproj? (instead of and
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to be able to opt into the double-eval even for a vcxproj if you really want to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Intentional.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Read that wrong. Read that as explicit skip and vcxproj.
than one framework. | ||
--> | ||
<ItemGroup> | ||
<_MSBuildProjectReferenceExistent Condition="'%(_MSBuildProjectReferenceExistent.SkipGetTargetFrameworkProperties)' == '' and '%(Extension)' == '.vcxproj'"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to be able to opt into the double-eval even for a vcxproj if you really want to.
@AndyGerlicher @rainersigwald
Customer scenario
Primary:
Referencing an SDK/CPS-based project from UWP project would behave incorrectly (pick wrong TFM of reference) or fail with incorrect incompatibility error.
Also:
Bugs this fixes:
#1474
#1390
dotnet/sdk#707
dotnet/project-system#477
Risk
Low.
Performance impact
Negligible.
Is this a regression from a previous update?
No.
Root cause analysis:
We missed the special cases around monikers for UWP.
How was the bug found?
Customer reported