Add visualizer support for the StringBuilder class in VS #80735
Merged
Conversation
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
dotnet-policy-service
bot
added
the
Community
tmat
approved these changes
Oct 15, 2025
This was referenced Oct 16, 2025
This was referenced Oct 18, 2025
This was referenced Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
We were investigating easy quality of life improvements for Visual Studio 2026 and determined that it would be a great idea to treat the
StringBuilderclass as a first-class citizen and allow it to be viewed via the string visualizers. This greatly improves the debugging experience by being able to see how the string is updated while debugging.There is nothing we can do to support this feature from the VS or Debugger source code since this capability is solely dictated by the result provider. Hence, this change.
I tested locally on .NET and .NET Framework applications to verify that the feature works as intended. Unit test passes locally too.