Download this extension from the Visual Studio Marketplace or get the CI build.
📖 Full documentation — detailed guides for every feature.
Stop wrestling with XML documentation comments. Comment Studio transforms how you write, read, and maintain code documentation in Visual Studio.
- Rendered Comments — View XML docs as clean, formatted text (no XML noise)
- Markdown Support — Use
**bold**,*italic*,`code`, and[links](url)in comments - Auto-Reflow — Automatically wrap comments to your preferred line length
- Collapse/Expand — Hide comment blocks to focus on code, expand when needed
- Color-coded Anchor Tags — TODO, HACK, BUG, FIXME, NOTE highlighted in distinct colors, plus custom tags
- Better Comments Style — Prefix-based highlighting (
!,?,*,//,-,>) for visual differentiation - Solution-Wide Code Anchors — Browse all TODOs, HACKs, and notes across your entire solution
- Clickable Issues —
#123links directly to GitHub/GitLab/Azure DevOps issues - Link Anchors — Navigate to other files, lines, or named anchors with
LINK:or uppercaseLINKsyntax - Comment Remover — Bulk remove comments with smart preservation options
- Theme-aware — Works with light and dark Visual Studio themes
Supports: C#, VB.NET, F#, C++, TypeScript, JavaScript, Razor, SQL, and PowerShell
See your documentation, not the XML. The Full rendering mode strips away XML noise and displays your docs with proper formatting.
TODO, HACK, BUG, NOTE, and more are highlighted with distinct colors. Uppercase tags can be written bare (TODO fix this); lowercase or mixed-case tags require : or ! (todo: or Todo!). Prefix-based highlighting (!, ?, *, //) provides additional visual differentiation.
Track all your TODOs, HACKs, and notes across your entire solution in one tool window.
#123 references become clickable links to GitHub, GitLab, Bitbucket, or Azure DevOps. LINK: syntax lets you navigate to files, lines, and named anchors; uppercase LINK may also be used without a delimiter.
XML documentation comments are essential for IntelliSense and API documentation, but they come with frustrations:
- Hard to read – XML tags clutter the actual documentation content
- Tedious to format – Manual line wrapping and alignment is time-consuming
- Visual noise – Long comment blocks obscure the code you're trying to read
- Easy to miss important notes – TODO and HACK comments blend into the code
Comment Studio solves all of these problems, letting you focus on writing great documentation instead of fighting with formatting.
- Install the extension from the Visual Studio Marketplace
- Open any C# or VB.NET file with XML documentation comments
- Try rendering modes – Use Edit > Comments to switch between Off, Compact, and Full rendering
- Try reflow – Edit a comment and use Format Document (Ctrl+K, Ctrl+D) to see automatic formatting
- Try collapsing – Press Ctrl+M, Ctrl+C to collapse all comments and focus on code
| Topic | Description |
|---|---|
| Comment Rendering | Rendering modes, rendered XML docs, Markdown formatting |
| Comment Reflow | Auto-reflow, Format Document integration, Smart Paste |
| Comment Outlining | Collapse and expand XML doc comments |
| Comment Tags | Color-coded tags, custom tags, prefix-based highlighting |
| Code Anchors | Solution-wide Code Anchors tool window |
| Issue Links | Clickable #123 issue references |
| Link Anchors | LINK: navigation syntax |
| Comment Remover | Bulk comment removal commands |
| Settings | All options and .editorconfig support |
| Fonts & Colors | Customizable Fonts & Colors reference |
This extension implements functionality requested by users on the Visual Studio Developer Community:
- Option to highlight TODO comments in the editor
- Different types of comments
- Color the TODO comment so it is different
- Enable links in comments that are relative
- Support for showing rendered documentation comments
- Support TODO comments in Visual Studio
If you enjoy using the extension, please give it a ★★★★★ rating on the Visual Studio Marketplace.
Should you encounter bugs or have feature requests, head over to the GitHub repo to open an issue if one doesn't already exist.
Pull requests are also very welcome, as I can't always get around to fixing all bugs myself. This is a personal passion project, so my time is limited.
Another way to help out is to sponsor me on GitHub.






