Released on 8/7/2021 11:43:21 PM
This update contains fixes for issues resolved since update 21.1.1053.
A hover tip has been added to the search box in light templates to advise on the available search wildcards and operators
See Also links can now have a target window identified
When creating See Also links in the Topic or Content File editors, a new "Open in window" option can be used to identify the window in which the link should open. A target attribute is also supported on .NET xml seealso comments for the same purpose - use a value of "_blank" to have links open in a new window.
Support for the href attribute added to see and seealso xml comments
Previously, limited support for linking to urls was provided through the !: prefix for cref attributes (which caused the c# compiler to not reject cref values). The href attribute is now the recommended method to link to urls and this is now fully supported for both see and seealso xml comments
.NET see links that point to uris will now default to opening in a new window
Many sites now prevent opening content in a frameset for security reason. The result of this is a page error when trying to navigate to an external uri from output generated using the frameset based classic and light templates. This change ensures that see xml comments that link to an external uri will open correctly in a new tab.
The version of jQuery, jQuery UI and secondary plugin libraries in the classic and material templates have been updated to the latest compatible version
A webservice WSDL import without a schemalocation causes a load error
Error loading a project referencing an open api / swagger definition with a schema containing 2 properties referencing the same type
Sizing of the popup for dynamic image widget with very large full size images improved
The popup will now expand to the full page width if required (was previously constrained to a max 900px width).
Language filter disappears in light template when all languages unticked
It is no longer possible to untick every language - one language must remain selected
Script error relating to ClipboardJS appears in generated outputs using the Colorized Example Code widget
Character alignment issues in acrobat viewer when viewing some PDF booklets
Released on 2/21/2021 5:38:14 PM
This update contains fixes for issues resolved since update 21.1.1047.
Light template does not adapt layout correctly in mobile browsers
The light template has been enhanced to better adapt to a mobile browser form factor
Exception when creating a new Document! X project directly from Visual Studio
Breadcrumbs link broken when another node references the same parent and one target is excluded by build flags
The result grid in the undocumented items report is blank
Youtube widget embeds the movie using http: when content is served over https:
Updated timestamp url used by the Microsoft Help Viewer outputs (the old timestamp url has been retired)
Released on 12/24/2020 10:11:47 AM
This update is the initial release version of 2021.1
Sql database documentation connections will now use MSOLEDBSQL (current generation OLEDB driver) when available
The "Find what" term is now highlighted when the find and replace dialog is shown
Add dark mode support to the Light templates
If this feature is enabled (it is enabled by default, but can be disabled on the Templates page in the Build Profile Editor) the light templates will automatically adopt dark styles when running in modern browsers (e.g. Chrome, Edge (Chromium), Firefox) when Dark Mode is enabled in the operating system (Chrome, Edge, Firefox) or in the browser settings specifically (Edge). As well as all of the standard template colors and styles, the colors used by colorised code sections are dynamically adjusted to ensure they are readable in dark mode. A CSS selector prefix of "html.i-dark" can be used to define style rules that apply specifically in dark mode - should you need to adapt your custom styles to work in both light and dark modes.
Updated Light templates to use latest package library versions
The Light templates now use jQuery 3.0.3 and jQuery UI 1.12.1 when targeting browser help output. When building CHM output, legacy versions of package libraries are automatically used as the Microsoft CHM Viewer runs in an Internet Explorer 5 context.
Compiled help and browser help are now prevented from being built in the same build profile
Xml schema information for xml document and content columns is now included in the datatype information for Sql Server documentation
Support for documenting from OpenApi 3.x definitions
Document! X now includes comprehensive support for documenting OpenApi 3.x definitions, from .json or .yaml files. New support in OpenApi 3.x includes documentation of inline schemas, array types, format subtypes and multiple request types.
NullReferenceException adding an OpenApi web service (fixed by implementation of OpenApi 3.x support)
Element removed when creating a bullet or numbered list with the cursor in an inline element
Exception when checking in to source control with multiple Content Files open
Error when creating a new template if the name field is left blank
Collapsible headings always appear at the bottom of the In This Topic list and not in the actual order in the document
font and u tags incorrectly applied to links when cutting / copying content if selection is applied from end to start
Words containing an accent character are not highlighted when navigating from search results
Added search operator tip text (advising that AND and OR can be used) below input box on search page in Light browser help output
Alias filenames used even if the option disabled in Build Profile when building a CHM output if a previous short filename mapping file exists
.NET types with EditorBrowsable.Never incorrectly included in .NET documentation when filter option enabled
Exception when editing the master.html page type
Improved french translation for "Highlight search terms" phrase in browser help templates
When applying an inline style to a table column, the style is only applied to the first cell in the column
In This Topic Widget does not use the standard template phrase ($$In_This_Topic$$) by default
Cannot scroll to the end of long content in the "Topic name" field on the CHM link page in the Link Designer