Goddamn it, if I wanted to throw an exception, I would do so. One other major annoyance I have been unable to disable is when I type:Īnd VS fills in the method body with a throw of some exception. ** Visual Studio Feature Request: I would like a single config which would turn _all_ that stuff off, at once. (I don't greatly object to color-coding, or in general features which change the _appearance_ of text, without actually changing the text.) In Visual Studio, I have gradually figured out how to turn most of them off, one by one. More generally, I dislike all editor features that change the actual text I type in any way. This is tedious moreover, if I later try to edit the comments in VS, it screws them up again. The best solution I have found to the VS commenting 'feature' is to load the source code into vim, which knows how to 'undecorate' the comments. They are a crutch for people who can't write, and for ignorant managers who just want to be able to pretend that documentation exists. So far as I am concerned, they are a mechanism for generating fake documentation, consisting of huge amounts of redundant junk with little real information.

Please don't tell me about the XML-commenting features of VS: I know about them, and don't like them (or Doxygen or any other 'documentation generators'). After I get WinWord to format the paragraphs, I have to find all the stray asterisks and remove them. WinWord), then reformat and edit them, to create documentation.

A) It makes paragraph-reformatting comments quite difficult and time consuming.ī) I like to write large, conceptual and overall descriptive comments in code, and later clip them out into other writing tools (i.e.

Visual studio auto format