Remove DebugProxy from WebAssembly Server package #63228
Draft
+2
−332
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.
This PR removes the Blazor WebAssembly debugging proxy functionality from the
Microsoft.AspNetCore.Components.WebAssembly.Server
package as part of the work to support issue #25643.Changes Made
Removed Files:
WebAssemblyNetDebugProxyAppBuilderExtensions.cs
- Extension methods forUseWebAssemblyDebugging()
DebugProxyLauncher.cs
- Debug proxy process launcher and managementUpdated Files:
UseWebAssemblyDebugging()
calls from:PublicAPI.Shipped.txt
to remove the debug proxy public APIImpact
The debug proxy functionality is no longer available through the WebAssembly Server package. This enables the debugging infrastructure to be moved to a separate location as planned in #25643, allowing VS Code and Visual Studio to download and use the debug proxy from an alternative location.
Applications that were using
UseWebAssemblyDebugging()
will need to be updated once the new debugging infrastructure is available.Fixes #31393.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.