[release/7.0-staging] [wasm][debugger] Using "RollForward": major for BrowserDebugHost#89962
Merged
thaystg merged 1 commit intorelease/7.0-stagingfrom Aug 14, 2023
Merged
Conversation
ghost
added
the
Contributor
|
Friendly reminder: if you want this servicing fix to be included in the September 2023 Release, you'll have to merge this PR before August 14th. |
thaystg
added
Servicing-approved
lewing
approved these changes
Aug 14, 2023
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 free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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 #89960 to release/7.0-staging
/cc @thaystg
Customer Impact
Testing
If the customer has only .net8 installed it's possible to run a BlazorWebassembly app targeting .net6/.net7, but it's not possible to debug it.
Fixes #88391
Risk
Low risk, only allowing the same version that is used to run DevServer to run BrowserDebugProxy.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging, notrelease/X.0.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.