What's new in VSdocman version 13.0:

1. NEW: Added support for VS 2026.
2. CHANGE: The links to .NET members in the chm_2025 documentation now open in the default browser. Previously, they opened directly in the CHM viewer, which could cause issues with modern pages, such as script errors. The CHM viewer uses an old rendering engine that lacks compatibility with newer HTML standards.
3. FIX: The VSdocman installer could incorrectly report that no installed version of Visual Studio was found, if also the 'SQL Server Management Studio 21' (preview) was installed. This has been fixed.
4. FIX: In some cases, when generating documentation for some projects (e.g., WPF) targeting .NET 6 or newer, dead links to .NET members were generated and reported.
5. FIX: Implicitly implemented methods/properties in C# (not explicitly implemented) were not recognized as implemented. This resulted in missing documentation that should be inherited from the implemented interface.
6. FIX: Comments from external code members (from referenced assemblies) that were inherited or implemented were not included in the generated documentation. For example, if a class implemented an interface from an external assembly, the comments from the interface members were not included in the documentation of the implementing class.
7. FIX: The table of contents in the generated PDF file was not properly updated in very rare cases. Instead, it showed the [Press ALT+A and F9 to update the TOC and other fields] text. This has been fixed.

What's new in VSdocman version 12.0:

1. NEW: Added support for projects that target .NET 6 and later. VSdocman worked with such projects even before, but only partially. For example, cref links to .NET types were not resolved.
2. NEW: Added support for C# global using directive. The global using and implicit global using directives were introduced in C#10 (with .NET6, but may be used with .NET Framework as well).
3. NEW: Added new output formats html_2025 and chm_2025. These are continuations of the older html_msdn2019 and chm_msdn2019, and it is recommended to switch to the new ones. Several improvements were implemented in the new templates, such as better responsiveness. The HTML output is more mobile-friendly now.
4. NEW: Added new Markdown output format which uses Github-flavored Markdown syntax. It is a simple text format which can be easily converted to HTML, PDF or other formats. It is suitable for version control systems like Git. You can use any Markdown editor to edit the files. The final documentation can be viewed in any Markdown viewer or converted to other formats. The main page is "index.md". It's especially suitable for Github wiki or pages. The table of contents is generated in "_Sidebar.md" file which is recognized by Github wiki. See an example.
5. NEW: Added support for Greek characters in CHM output. You just need to select the "el-GR" language in the output format options.
6. FIX: The comment editor and "Add XML comment" didn't work with shared projects (.shproj).
7. FIX: Dead links were reported when the documentation was generated, if there were "using" statements in C# (or "Imports" in VB) with an alias. For example, using Point = System.Drawing.Point. Then the links starting with the alias would fail with the warning, for example, <see cref="Point3D">.
8. FIX: When an <inheritdoc> or <include> XML doc tags imported multiple XML elements, they were inserted in the reverse order. This was not a problem if the imported elements were top-level elements, such as <summary>, <remarks> and others, because their order is not important. But if the imported elements were, for example, <para> tags inside a <remarsks>, they were in the wrong order in the generated documentation.
9. FIX: When compiling documentation from command line with VSdocmanCmdLine.exe using VS 2017, a "Could not load file or assembly EnvDTE" exception could occur.
10. FIX: The html_msdn2019 and chm_msdn2019 output didn't work correctly if there was an <svg> element injected in the documentation. An SVG element can be added in the header, footer or any other part of the page, see "Using HTML and Unknown Tags in XML Comments" topic in the help.
11. FIX: An unhandled exception message could be displayed if the user moved the mouse cursor out of the comment editor. This was harmless but annoying.

What's new in VSdocman version 11.2:

1. NEW: The highlighted notice "API is not CLS-compliant" is displayed for members with CLSCompliant(false) attribute.
2. NEW: Added support for private protected code members. They were incorrectly recognized as protected previously.
3. FIX: Visual Studio 2022 could crash if "Browse" button was pressed for Output Folder, External Files Folder or Templates Folder in VSdocman "Output" project properties. Other VS versions were not affected.

What's new in VSdocman version 11.1:

1. FIX: Some links were not resolved correctly when a "using" statement in C# or "Imports" in VB was used. The issue was introduced in version 11.
2. FIX: The "Select reference" dialog in the comment editor didn't contain members from referenced assemblies. The issue was introduced in version 11.
3. FIX: In rare cases, some class diagrams, and possibly also some source files, failed to compile if the documentation was compiled from command line using VSdocmanCmdLine.exe utility.

What's new in VSdocman version 11.0:

1. NEW: Added support for VS 2022.
2. CHANGE: Removed support for VS 2013 and VS 2015. Only VS 2022, 2019 and 2017 are supported now.
3. CHANGE: Removed /vs parameter from VSdocmanCmdLine.exe command line utility. This parameter was used only with VS 2013 and 2015 that are no longer supported.
4. CHANGE: VSdocman now installs to "C:\Program Files" folder by default, instead of "C:\Program Files (x86)". So if you are using the command line version, change the path to VSdocmanCmdLine.exe utility or install VSdocman to the original x86 folder.
5. FIX: The WYSIWYG comment editor added an extra newline at the end of a <code> block in some cases.
6. FIX: The html_msdn2019 output was not rendered correctly (the left tree was missing) if it was viewed online in Chrome with some extensions installed. For example, Grammarly was such a problematic extension.
7. FIX: Improved search results in html_msdn2019 output format. If a topic title contained the searched word, it was not listed at the beginning of the search results if there were other topics that contained this word too many times in their text.

What's new in VSdocman version 11.0:

1. NEW: Added support for VS 2022.
2. CHANGE: Removed support for VS 2013 and VS 2015. Only VS 2022, 2019 and 2017 are supported now.
3. CHANGE: Removed /vs parameter from VSdocmanCmdLine.exe command line utility. This parameter was used only with VS 2013 and 2015 that are no longer supported.
4. CHANGE: VSdocman now installs to "C:\Program Files" folder by default, instead of "C:\Program Files (x86)". So if you are using the command line version, change the path to VSdocmanCmdLine.exe utility or install VSdocman to the original x86 folder.
5. FIX: The WYSIWYG comment editor added an extra newline at the end of a <code> block in some cases.
6. FIX: The html_msdn2019 output was not rendered correctly (the left tree was missing) if it was viewed online in Chrome with some extensions installed. For example, Grammarly was such a problematic extension.
7. FIX: Improved search results in html_msdn2019 output format. If a topic title contained the searched word, it was not listed at the beginning of the search results if there were other topics that contained this word too many times in their text.

What's new in VSdocman version 10.0:

1. NEW: The WYSIWYG comment editor is now available also for external XML doc files that are included with <include> XML doc tag. It is available from the comment editor, Advanced tab. There's new "Editor" button in the include section.
2. NEW: The option to always open VSdocman window with SOLUTION-WIDE PROPERTIES instead of the project that is active in Visual Studio. It's in VSdocman Options > Miscellanous > General.
3. CHANGE: XML comments, such as <summary><!-- this is comment --></summary> inside XML doc comments are allowed now. Unlike before, they are not outputted in the generated documentation now. The WYSIWYG comment editor will preserve such XML comments too.
4. CHANGE: The comment editor will generate &#160; entity for a non-breaking space. This is to easily distinguish it from a normal space.
5. CHANGE: The comment editor will no longer generate &quot; and &apos; entities for " and ' characters in XML text. Such escaping is needed only in XML attributes and not doing it in the text will make XML comments more readable.
6. CHANGE: The comment editor did not open if the active document was under source control (TFS) and was not checked out. The editor will now check out automatically, if the "Check out automatically" when editing is selected in VS source control options.
7. CHANGE: When the user inserts a table or a code block in the comment editor, an empty paragraph is added before and after it if needed, to ensure that it's possible to enter text there.
8. CHANGE: Links to enum items, such as <see cref="MyEnum.Value1"/>, are no longer generated as non-link bold text. The link to the owner enum is generated now.
9. CHANGE: The values of enum fields are now displayed in generated html_msdn2019 and chm_msdn2019 output formats.
10. FIX: If a type, e.g. a class, was excluded because it had no XML comment and "Compile also non-commented members" option was not selected, its members such as methods and properties were still included in the documentation. They were not available in the contents tree, but they could be visible in search results.
11. FIX: The errors in external XML doc files were not reported during compilation. Such external XML files are included with <include> XML doc tags and they can cause various problems - IO error, invalid XML syntax, etc.
12. FIX: XML errors in custom topics were not reported during compilation. This could happen if the user edited the XML source of the topics directly instead of in the WYSIWYG editor.
13. FIX: "Dead link" warnings in custom topics were not reported during compilation.
14. FIX: In custom topics (not in code members), the links to methods with parameters were not generated correctly in the final documentation, for example <see cref="Ns1.Class1.Method1(Ns1.Class1)"/>.
15. FIX: "Dead link" warnings occurred for incomplete links to generic methods with parameters excluded. For example, <see cref="Ns1.Class1.Method1{T}"/>.
16. FIX: Visual Basic properties, that had no explicit access modifier (Public, Private, ....) and were not auto-implemented (had Get and Set parts), were not included in the generated documentation.
17. FIX: Whitespaces between inline tags in XML doc comments were removed in the WYSIWYG comment editor and in the comments coming from external XML files included with <include> tag. For example, the space between A and B in: <summary><b>A</b> <u>B</u><.summary>.
18. FIX: The WYSIWYG comment editor added an extra space character after a <br/> tag.
19. FIX: When the user added an exception or a permission in the WYSIWYG comment editor, it was not possible to edit the text in it and the <exception> or <permission> tag was not inserted in the generated XML comment.
20. FIX: An extra empty <see> tag could be added after editing an existing link in the WYSIWYG comment editor.
21. FIX: When the user clicked on a link in the WYSIWYG comment editor, the page was scrolled down to the end of the editable section in some cases.
22. FIX: Some combinations of special XML characters in XML comments could produce wrong result in the generated documentation. For example, <summary>&amp;lt;</summary> would produce "<" instead of "&lt;".

What's new in VSdocman version 9.10:

1. FIX: Improved processing of an empty <inheritdoc/> tag when it was inlined within another XML doc tag, for example, <remarks><inheritdoc/></remarks>. In such a case, any plain text from the base member was lost and only child XML elements were inherited, e.g. <para>. Moreover, if the <inheritdoc/> tag was used inside a <param> tag, the aggregated contents from all <param> tags in the base member was included.
2. FIX: A dead link was generated for a <see> or <seealso> link in VB that was in form of cref="AAA.BBB.BBB" for class BBB in namespace AAA.BBB.
3. FIX: An error occurred during documentation compilation, if there was a type with no namespace (e.g. a class directly in the empty <default> namespace) and no language was selected for generating the syntax in VSdocman options.

What's new in VSdocman version 9.8:

1. NEW: New chm_msdn2019 output format was added. It has a modern look like the current online MSDN.
2. NEW: The command line utility VSdocmanCmdLine.exe displays the VSdocman version and the version of Visual Studio that is used in the background.
3. FIX: Visual Studio could crash when VSdocman tried to compile documentation for .NET Core 3.1 projects. This could also happen also for other project types but only in very specific cases. For example, an UWP application that targets Win 1809 and uses HockeySDK.UWP 4.1.6 Nuget package. The problem was related to a VS issue and occurred only when some specific versions of assemblies were referenced by the documented project. For example, it was not present with some .NET Core 3.1 updates.
4. FIX: A "dead link" warning occurred for <see> or <seealso> links in some cases.
   Case 1: the cref pointed to a method with a ref/out (ByRef in VB) array parameter, for example cref="Method(ref int[])".
   Case 2: the cref pointed to a method with a multidimensional array parameter, for example cref="Method(int[,])".
   Case 3: the cref contained some of the language specific data types - sbyte, uint, ulong, ushort in C# and Date, SByte, UInteger, ULong, UShort in VB.
   Case 4: the cref was a link to a constructor in a language specific format, for example "Object.Object()" in C# or "Object.New()" in VB.