Uh oh!
There was an error while loading. Please reload this page.
[release/7.0] Explicitly omit RID from crossgen2 binary path - #78735
Merged
Conversation
jkotas
commented
Nov 23, 2022
Member
@carlossanlop Can this be merged? |
carlossanlop
commented
Nov 23, 2022
Contributor
Assuming this change does not need OOB package authoring changes, then it's ready, but I'll merge it when the branch reopens. |
carlossanlop
commented
Nov 23, 2022
Contributor
Actually, it's blocking the build and it's only infra. I should merge. |
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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Backport of #78733 to release/7.0
/cc @jkotas
Customer Impact
Fix source-build build break. Compensate for breaking change in .NET SDK 7.0.200.
Infrastructure only fix.
Testing
Verified locally that the build break is fixed
Risk
Low
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.