13 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Hari commented  ·  July 26, 2012 3:37 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  If this gets implemented, I sure hope it'll be optional, and non-default setting.

• Knowing me, knowing you, a-ha commented  ·  July 25, 2011 2:49 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @Anonymous I cannot agree with that. When I read code I read comments with it as something natural, and actually helpful.
  Agree that there should be option to hide show comments but that's bit different to what you're saying.

• Steve commented  ·  July 21, 2011 7:06 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Eric, nobody is saying the comments are not of value. That's why this is a suggestion to simply display the comments in a manner which is unobtrusive.

• Eric commented  ·  July 20, 2011 11:07 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  That sounds like "well-documented, easy to maintain 6 months from now when we give it to the intern" code to me.

• Steve commented  ·  July 20, 2011 12:07 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  If you've ever gone down the path of creating XML comments for every public method, property and so on... or turned on Stylecop and accepted it's guidance to also create these for every private method and private member variable. Quickly your class has 5 lines of comments for every line of code.

  So yes, comments become noise.

• Eric commented  ·  July 20, 2011 10:41 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  "Anything in a source file except code is noise"

  Seriously? Comments are the single most important thing you can do to make code more readable and maintainable. Hiding them is a horrible idea.

• EricTN commented  ·  July 16, 2011 2:59 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Can't agree with the "anything in a source file except code is noise" assertion. Guess it comes down to a matter of style/taste. I suppose if this was an option that could be switched-off so the comments are visible as written, it would be ok.

• Peter Jones commented  ·  July 14, 2011 1:42 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I find a lot of value in having comments in-line to break up a large chunk of strange code - it makes it much more visual obvious where methods start and end if you can see the green text wizz past while scrolling. Of course, there may be better ways to achieve the same experience.

  Also you can already use #regions to hide and organise stuff.

• Jon Davis commented  ·  July 14, 2011 11:51 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Would be a useful extension if one doesn't already exist. I don't see it necessary as part of the prebuilt VS.

• The configurator commented  ·  July 14, 2011 11:01 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I definitely agree, but like Dave Sussman said - only for XML comments.

• Dave Sussman commented  ·  July 13, 2011 3:14 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This would be really useful for XML comments, which I like for IntelliSense help, but hate because of the noise.

• Andrew Olson commented  ·  July 13, 2011 2:42 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I agree with irperez; this should be an option.

• irperez commented  ·  July 13, 2011 8:57 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'm not crazy about this idea. I'd rather this be an option rather than the rule