Latest News

VSdocman 7.3 released

We are glad to announce that the new version 7.3 of VSdocman has been released. VSdocman is a  Visual Studio tool for a quick commenting and automatic generation of technical documentation from your C# and VB .NET projects. For more information go to VSdocman home page .

This minor update adds some new features and improvements. You can download it from here. If you have installed VSdocman 6.8 or earlier, uninstall it before installing the version 7.3.

What's new in VSdocman version 7.3:

  1. NEW: Added complete traditional Chinese translation for generated documentation. Just select zh-TW as the language in the output options.
  2. NEW: You can specify topics version for the MS Help Viewer format. See VSdocman's help, Viewing and Deploying Documentation - View and Deploy MS Help Viewer Documentation - Topic Versions in MS Help Viewer Documentation page.
  3. CHANGE: In web site projects without a project file (not web applications), the $(ProjectDir) macro in the output options has a different value. Previously it was the directory constructed from <SOLUTION_FOLDER>\<WEBSITE_NAME>. Now it points just to <SOLUTION_FOLDER>. So if you have a web site (not a web application with a project file) and you specified the Output folder as $(ProjectDir)VSdoc, you need to change it to $(ProjectDir)<WEBSITE_NAME>\VSdoc, where <WEBSITE_NAME> is the name of your web site project.
  4. FIX: The links that contained an ampersand (e.g. <see href=""/>) were generated incorrectly.
  5. FIX: The link to the parent namespace was not generated in a code member topic, if the namespace was a root namespace in the project.
  6. FIX: In VB .NET, external methods defined with DllImport attribute instead of Declare statement were not recognized as external.
  7. FIX: Links to external methods (defined with DllImport attribute) were not generated correctly.
  8. FIX: If an event in VB .NET was defined with an explicit generic delegate, e.g. Public Event TextChanged As EventHandler(Of TextChangedEventArgs), the syntax section in documentation was generated incorrectly.
  9. FIX: If a method in a class implemented a method in an interface, the comment for a method was incorrectly inherited if the interface contained multiple method overloads, i.e. methods with the same name but different parameters. This happened when you for example clicked "Add XML comment" for the method in the class.
  10. FIX: The blank lines inside a <code> tag that were inserted in the comment editor were not included in the XML comment.