Documenting has never been so easy

We are glad to announce that the new VSdocman 9.6 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 source code files. For more information go to VSdocman home page .

This minor update fixes some little problems. You can download it from here.

What's new in VSdocman version 9.6:

  1. FIX: In the generated list of class constructors, there were listed also the constructors from the base classes. This was wrong because constructors cannot be inherited.
  2. FIX: Some inherited methods and properties were listed in the generated Methods or Properties lists even if the 'List inherited members on "Class members" page' option was deselected. The problem applied only to the inherited members that were defined in the solution. External inherited members were not listed, e.g. ToString() method from Object class.
  3. FIX: If you created a new solution profile with VSdocman profile manager as a copy of another profile, the solution-wide properties were not copied. The default properties were applied instead.
  4. FIX: Wrong formatting after pasting parts of ordered or bulleted lists in the WYSIWYG comment editor. If only some items of a list were copied in the clipboard, then they were incorrectly rendered if they were pasted in the edited text that was not a list.
  5. FIX: A linebreak entered with Shift+Enter was displayed as an unknown <br/> XML doc tag with the blue highlighting when it was reopened in the WYSIWYG comment editor. Now there's a correct new line displayed.
  6. FIX: Improved pasting of a source code to a code section in the WYSIWYG comment editor. For example, if a source code sample was pasted, e.g. from VS editor, empty lines were removed. Or when lines from one code section were copied to another one, the linebreaks were lost.
  7. FIX: In some cases, a dead link could be generated for <see> or <seealso> links containing methods with specified parameters. This happened in two cases. The first one was, if there existed a method or a property with the same name as the parameter type of the referenced method. For example, the link was <see cref="Method1(Action)"/> and there was also a method like the following one defined in the same class: void Action(). The second case was, if the referenced method was in another class than the comment with the link and the link was not in a full format, i.e. including the namespace.
  8. FIX: In Visual Basic code, a dead link was generated for <see> links containing the names inside square brackets. This syntax is used in VB for symbols that are same as the VB reserved words, such as Enum, ByVal, etc. For example, there was a method defined as follows: Sub [Enum](x As [Enum]). The corresponding link could be: <see cref="[Enum]([Enum])"/>. Such links are processed correctly now.
Cookies user preferences
We use cookies to ensure you to get the best experience on our website. If you decline the use of cookies, this website may not function as expected.
Accept all
Decline all
Set of techniques which have for object the commercial strategy and in particular the market study.