Italicize comments.

(25) Review
Visual Studio
2013, 2012, 2010
Download (47,391)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (25)
Q and A (6)
Sign in to write a review
Sort by:

by CBecks | August 25 2014

Your comment about "not consolas" is asinine.

Rated 2/5 because it's still a very useful plugin, once you've taken the time to recompile it without with arrogance.

Noah Richards August 25 2014
| Edit |

Consolas doesn't have good-looking italics, really just because fixed width fonts generally look bad italicized. The fixed width lucida fonts would have been equally as bad to read :-/ I'm not sure that's an arrogant thing to point out, though I did get a laugh out of you taking the time to call both the comment asinine and point it out on a public review site, so thanks for that :-p

by Mikael Nygaard | September 06 2013

Been using this extension since VS2010. Everytime I use a fresh VS installation, this extension is one of the first I install. Can't live without it.

Great and simple.

by Guilherme Morais | June 05 2013

simple, works great. Thanks!!!

by Heinz Wrosch | January 07 2013

I like this extension very much. This awful hard-coded font, however, is a no-go! PLEASE make it configurable, or at least don't change the VS default font. As it seems, not many people share your taste...

by SWAT555 | October 12 2012

by Andre.Ziegler | September 13 2012

must have tool to better read comments. Thanks :)

by Jens Vestergaard | August 07 2012

by TejasJ | January 10 2012

My code is much more readable...

by Ehsan Mohammadi | October 08 2011

The Idea is perfect!

by Marco Ragogna | May 31 2011

The idea is nice, but hard-coded font family is annoying.

by Aravind PK | April 26 2011

feature is nice. But as many commented, it has static font and it would be good if customized on default commenting.

by manoj1407 | March 23 2011

by JoeArmonic | December 30 2010

Great! I love the way it clarify the reading and code understanding. I'm impelled to write more comments now.

by atconway | November 02 2010

Just makes XML comments stand out so much nicer. I really like this extension.

by SavasP | October 22 2010

by Robert Vuković | July 27 2010

Hard coded font -> Ugly

by KMASubhani | May 28 2010

Nice extension, first one I installed.

But, I don't think it should modify the font size specified in Fonts and Colors-> Text Editor-> Comment
I would still like to be able to read the comment, when I need to.

by Pent Ploompuu | May 04 2010

by Pascal Craponne | April 24 2010

The addin works just well, but we do not apparently share the same taste with the author (I like italic consolas).
My suggestion: italicize the font configured in Visual Studio text configuration instead of using hard-coded Lucida sans.

by Troy Goode | April 23 2010

1 - 20 of 25 Items   
Sign in to start a discussion

  • VS 2015 support?
    1 Posts | Last post July 21, 2015
    • Do you have plans to support VS2015?
  • VS 2013 Availability??
    2 Posts | Last post November 10, 2013
    • When will this be available for VS 2013?  There are other comment format modifier extensions, but this is the one I want!!  :-)
    • 2.2 should now support VS2013. Let me know if you run into any issues, thanks!
  • VS2012 problem
    3 Posts | Last post September 25, 2012
    • I get this error in VS2012 when opening a .cs file containing comments:
      <source>Editor or Editor Extension</source>
      <description>System.ArgumentOutOfRangeException: size should be positive or null&#x000D;&#x000A;Parameter name: size&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Formatting.TextFormattingRunProperties..ctor(Brush foreground, Brush background, Typeface typeface, Nullable`1 size, Nullable`1 hintingSize, TextDecorationCollection textDecorations, TextEffectCollection textEffects, CultureInfo cultureInfo)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Classification.Implementation.ClassificationFormatMap.CreateTFRPFromRD(ResourceDictionary dictionary)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Classification.Implementation.ClassificationFormatMap.GetTextProperties(IClassificationType classificationType)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Classification.Implementation.ViewSpecificFormatMap.GetTextProperties(IClassificationType classificationType)&#x000D;&#x000A;   at ItalicComments.FormatMapWatcher.Italicize(IClassificationType classification)&#x000D;&#x000A;   at ItalicComments.FormatMapWatcher.FixComments()&#x000D;&#x000A;   at ItalicComments.FormatMapWatcher..ctor(ITextView view, IClassificationFormatMap formatMap, IClassificationTypeRegistryService typeRegistry)&#x000D;&#x000A;   at ItalicComments.ViewCreationListener.&lt;&gt;c__DisplayClass1.&lt;TextViewCreated&gt;b__0()&#x000D;&#x000A;   at Microsoft.VisualStudio.Utilities.PropertyCollection.GetOrCreateSingletonProperty[T](Object key, Func`1 creator)&#x000D;&#x000A;   at ItalicComments.ViewCreationListener.TextViewCreated(IWpfTextView textView)&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Editor.Implementation.WpfTextView.&lt;&gt;c__DisplayClassc.&lt;BindContentTypeSpecificAssets&gt;b__9()&#x000D;&#x000A;   at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call)</description>
    • Forgot to say that it is not reproducible, sometimes I get this error, sometimes not, but I get it 3 times a day, enough to be annoying ;-)
    • That does sound annoying :-/ Since I don't have access to the editor implementation anymore, I'm not sure why this would be a new issue in VS2012, but I'll ask around. Thanks for reporting!
  • Visual Studio 2008
    5 Posts | Last post June 08, 2012
    • Do you think it's possible to have this add-on for VS2008 too?
    • There are addons that fake italics for VS2008, but this extension won't work there, since (1) extensions are VS2010+ and (2) this relies on the new VS editor introduced in VS2010. Sorry :(
    • Hi, Could this be modified to work in VS2012 rc  ?
    • I'm not sure if/when I'll get around to updating it. You can enable it for VS2012:
      1) Download the extension
      2) Change the file extension to .zip and unzip the contents
      3) Modify the extension.vsixmanifest, adding a new entry under the SupportedProducts group:
        <!-- VS10.0 is here, below it add: -->
        <VisualStudio Version="11.0">
      4) Add everything back to a .zip file, change the extension to .vsix, and open it from explorer
    • Thank you -I'll try that out!
  • source code
    7 Posts | Last post October 21, 2011
    • Is there any chance to make source code available ?
      Honestly this extension doing thing, that I would like to see how it's done.
    • Yes, that is definitely my intent :)
      You can also follow my blog over on - I'll be writing a few posts about these extensions in the near future.
    • Hi,
      How to install this valuable addons?
    • Hi, Noah,
      how to UNINSTALL this addon? :-)
      I want comments to be italics, BUT fixed-width.
    • I would suggest grabbing the code for this ( and modifying it to pick a different font (or just not override the font).  Look here for the code that sets the font:
    • Here's what I did to keep the font the same as the VS default:
      - Download the source from github (as mentioned by Noah above)
      - Make sure you have the Visual Studio SDK installed
      - Load the solution
      - Change line 129 to read:
        var newTypeface = new Typeface(properties.Typeface.FontFamily, FontStyles.Italic, FontWeights.Normal, typeface.Stretch);
      - Build
      - Go to bin\Release (assuming you built as a Release build)
      - There's your new vsix
    • This is what I have been looking for! Thank you Noah for sharing it with us, and Jason for the tip. Because although the hardcoded font isn't bad, I use a rather specific font.
  • Is it possible to do NOT format the spaces/tabs before any comment?
    2 Posts | Last post January 29, 2011
    • Hi,
      I use this extension a longer time, but it is annoying reading /**...*/ doxygen comments, where this extension does NOT format the spaces before the start of the comment block, while it formats the leading spaces of each line in the rest of the comment block.
      Is it possible, that this extension ignores in a comment block the "leading" spaces (^[[:space:]]+)?
    • It's possible, but it isn't that simple.  The extension doesn't re-classify comments, it changes the formatting information for comments themselves.  The reason why it looks crappy in that case is because the language service itself is classifying that whitespace as a comment, and the extension can't change that.
      However, this extension (or another) could have a separate classifier that only classifies the whitespace at the beginning of lines to try and override any font face/size changes.  The problem there is that there isn't a static way of declaring the formatting information for this classifier to override/undo lower-priority formats to be the same value as a different format (i.e. plain text).  It would have to hardcode the default font face/size and then write a component that watches for changes to the default and applies that to the whitespace override format.
      That's a pretty longwinded excuse, I know :-/  I'll be pretty busy the next few weeks, so I don't know if I'll get to look into anytime soon, but I'll try to find some time.
      Thanks for your feedback :)