-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix Source Link cross-targeting targets #33292
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
Conversation
@dsplaisted PTAL |
Can you please add a test that protects the behavior for multi-targeting and non multi-targeting projects? |
@ViktorHofer Will do that as a follow-up: #33297 |
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.
Looks good I think. Is there a reason not to add the tests with this PR as opposed to later? It seems like that would give more confidence.
src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.SourceLink.props
Show resolved
Hide resolved
To unblock Arcade updates ASAP. I might be able to add the test today though. |
Arcade is blocked anyway for about a month until the next (signed) preview that contains this fix releases. We meanwhile reverted the PackageReference change in Arcade. |
OK, go ahead and merge if you'd like. |
Added a test - figured I can reuse the existing one, just add packaging validation. |
IsCrossTargetingBuild
is only defined in.targets
, not in.props
.Only
Microsoft.SourceLink.Common.targets
needs to be imported in cross-targeting build as it contains workaround for dotnet/msbuild#3294. Once this issue is fixed we can remove cross-targeting specialization entirely.Related: dotnet/msbuild#8898
Fixes #33297