[release/8.0-staging] [browser] Fix debugger support #98494
Conversation
maraf
added
arch-wasm
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
/azp run runtime |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Friendly reminder that Monday March 11th is the Code Complete date for the April Release. If you want this change to be included in that release, please make sure to mark it as ready for review, get a code review sign-off, get a green CI (or confirm the issues are unrelated), and send an email to Tactics requesting approval. Otherwise, it will have to wait until the May Release. @maraf |
|
Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it. |
|
@maraf friendly reminder that code complete for the August Release is July 15th. If you want this fix to be included in that release, please merge this PR before that date. |
|
Friendly reminder that Monday July 15th is Code Complete day, that's the deadline to get this included in the August Release. |
|
/azp run runtime |
maraf
requested review from
radical,
lewing,
pavelsavara,
kg and
marek-safar
as code owners
jeffschwMSFT
added
Servicing-approved
|
@guardrex Since 8.0.9 the original behavior from .NET 7 will be restored, can you please update the docs for .NET 8 |
Migration of #97213 (also #100675 and partially #104361)
Fixes #102307
Customer Impact
Fixes several customer reported issues regarding custom configuration name and ability to debug application.
Regression from unification of Blazor SDK and former runtime Wasm SDK from .NET 8 cycle.
Testing
Automated tests for all scenarios (build, publish, implicit and explicit values)
Risk
Low