title: Best way to add developer documentation to your Visual Studio projects
body: <p>Basically, the question is: <em>Where (and in which format) should I store textual developer documentation associated with my Visual Studio projects?</em></p>
  
  <p>To elaborate: XML comments are great, but they don't cover all use cases. Sometimes, you'd like to describe the class architecture of the project at a high level, add usage notes to your library or just leave any other kind of message to future generations of developers working on this project.</p>
  
  <p>I'd like to add these documents directly as files into the Visual Studio project, to ensure (a) that they are available to the developer without further searching and (b) they are version controlled (using the same svn/git/whatever repository as the source code).</p>
  
  <p>Currently, I add a folder <code>_Documentation</code> to the project and use text files, but I'm not sure if this is the best solution. Visual Studio does not have an option for automatically word-wrapping text<sup>1</sup>, and manually fixing line breaks after each change is annoying. On the other hand, Word documents don't work well with version control, and TeX is too much of a hassle to set up and teach on each developer PC.</p>
  
  <p>Is there a well-established best practice for this?</p>
  
  <hr>
  
  <p><sup>1</sup> I know that there's Edit/Advanced/Word-Wrap, but this only affects the display, not the file itself.</p>