fix(vs): Remove VS reload project on TFM for browserwasm target #19454
Conversation
This file contains 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
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19454/index.html |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
In VS, when moving to/from the browser TFM, reloading is needed for debugging to work properly, so that the browserwasm TFM becomes first and VS shows the proper debugging UI.
What is the new behavior?
Placing the
DotNetCoreWebon all TFMs makes the debugging capabilities always available, removing the need to move thebrowserwasmTFM first. The only side effect is that now, when there's abrowserwasmTFM in the list, the project in the solution explorer will have a "web"-like appearance.closes #16516, closing #16525