This update contains fixes for issues resolved since update 15.2.68.
This update contains a revised digital signature to prevent SmartScreen errors when installing.
This update contains fixes for issues resolved since update 15.2.51 together with some enhancements.
\"Content from Web Page\" topics and widgets now support relative paths (relative to the project directory)
NamespaceDoc and AssemblyDoc Namespace and Assembly documentation placeholders are now supported in .NET xml comments
.NET Xml comments do not natively support content for Namespaces and Assemblies. In order to work around this limitation, Document! X will now look for a summary Xml comment in a \"NamespaceDoc\" class (which can be marked with the CompilerGenerated attribute) for the Namespace summary and in an \"AssemblyDoc\" class (in any assembly) for the Assembly summary.
Project Find and Replace, Link Check and Spell Check will now show a warning box if opened with a Locale different to the current Locale
As these tools use the Locale that is active when they are opened it was previously possible to inadvertently run these tools in a different Locale to the current one (i.e. Open Find and Replace when the Locale was set to the Primary Locale, change to a secondary Locale and then come back and run Find and Replace). The warning box identifies that the Locale the tool will use is different from the currently active locale.
A new \"Include Numeric Values in Enumeration Member Lists\" option has been added to the \".NET Settings\" page in the Build Profile Editor
This new option will enable you to automatically include numeric values in the Member Lists for Enumerations. Direct use of enumeration numeric values is discouraged in .NET but there are scenarios in which this information is required (i.e. for .NET interop with other systems and languages).
Document! X has now completed the Microsoft tests for Windows 10 Certification
See Also link to a website does not show the link caption in Web Service, Database and XSD Documentation projects
Intermittent exception during import
Exception when creating a new project if the target project could not be created in the selected path
Intermittent exception during import when running in 64bit version
Excluded types are included in namespace hierarchy if they inherit from an included type
Crash when opening the topic editor in a project containing a .NET assembly with a large interface inheritance hierarchy
Find Unused Images tool was previously only checking the current Build Profile. All Profiles are now checked.
Exception when right clicking on a missing image in the Topic Editor
This update contains fixes for issues resolved since update 15.2.49.
This update contains fixes for issues resolved since update 15.2.33 together with some enhancements.
Database documentation now supports multi line TSQL source comments
Comments can appear in the same or separate multi line comment blocks. Example:\r\n/* ##SUMMARY Summary content\r\n ##REMARKS Comments can flow \r\n onto separate lines\r\n*/\r\n/* ##RETURNS Multiple multi line comment blocks can be used, \r\n or all comments can be included in a single block\r\n*/
Added an "Edit Content File" context menu item to child documentable items on the Project Explorer to easily open the Content File Editor and navigate to that item
Search results in web output are now always visible if highlight search results option ticked, even if contained in a Drop Down section or Collapsible Heading Widget
Exceptions reported from the Build Results window (or other "Report Error" buttons) will no longer cause the application to terminate
Automatically constrain the size of the dynamic image widget overlay to the available window size
Will now prompt for a custom caption when creating a new Toc Heading node
Ability to document Azure Sql Databases, including the latest v12 version
When building a CHM output, the Html Help Compiler fails if Topic or reference documentation items contain non ASCII characters
The Microsoft Html Help Compiler used to create CHM outputs does not support unicode and throws an error if a content filename contains non ASCII characters (such as umlauts). This change attempts to work around this limitation by substituting such characters in the output filenames.
Broken links after importing from a Help 2.x project (.HxC file)
Exception when generating Microsoft Help Viewer .NET documentation if the the option to generate a .NET xml comment file is enabled and content contains links to .NET framework members
Additional elements inserted into page content when indenting / outdenting certain bullet or numbered list items
.NET Xml comment files are not automatically reloaded when they change on disk, so comments shown in the Content File Editor can sometimes be out of date
Error dialog when adding a new Web Service to a project if an incorrect web service definition type is specified
The advisory message on the error dialog has been improved to suggest double checking that the correct Web Service Definition Type and location have been specified when a load error is encountered.
A newly created bookmark is not available as the target for a new table of contents node, hyperlink or See Also link
Removed non functional Twitter widgets in the Internet Feed Widget Pack and replaced with a new Twitter Widget
Changes in the Twitter API rendered the previous Twitter Search Feed and Twitter User Feed Widgets non functional. They have now been removed and replaced with a single Twitter Widget in the main Widget list that uses the new Twitter Widget mechanism which is fully supported by Twitter.
When creating a new project from Visual Studio, VC++ assemblies may not found if the output path contains the $(Configuration) placeholder
"Remove Unused Images" tool identifies images used in a Content File with localization disabled and primary locale excluded
Images are not refreshed in an open Topic or Content File editor when updated or replaced on disk
See Also link category for reference documentation items is not always a consistent default
See Also links created in Topics to reference items, and See Also links to Topics created directly from the New button embedded in the Content File editor create See Also links with a blank category. This change sets the category to \"Link Target\" - i.e. for reference links in Topics the default category will be \"Reference\" and for Topic links created in reference topics the target Topic's Category will be used.
Shortcut link / cref generated by Comment Editor for C++ source uses \".\" instead of \"::\"
Source Control Errors when deleting and then immediately adding back images from the same location
Exception switching to a secondary locale in a project with multiple custom Document! X Placeholder Table of Contents Nodes
WidgetContentFromFile topic in the online help contained a typo
CHM prompts to download first script file if an invalid (removed or excluded) Default Topic is defined in the Build Profile
Search term not highlighted when using full text search in web output on local drive rather than web server
Load error when a @namespace comment is associated with a conditional assignment
Order of buttons on the Content File Editor toolbar incorrect for .NET - private and friend are first, rest further over
Exception when trying to add a Web Service using a WADL definition
Build exception if a Topic contains an Include Topic widget with a missing source property
After dragging and dropping Table of Contents nodes, the order of the dropped nodes is sometimes reversed
Exception when publishing web help if the build output directory is set to the \\build project sub-directory root
Exception when trying to document a Sql Database hosted on Azure
XSDs disappearing in a project containing both WSDL Web Services and manually added XSDs
Exception when using "Where is this used" functionality in a project that generates very long filenames
Nested Content Snippet are not shown when the nested snippet is already present elsewhere on the page
Error 500 - Fail on Install when registering a Microsoft Help Viewer output
Link Designer dialog does not show topic bookmarks with just the id attribute set
Data Type column in SOAP Web Service parameter table is \"(undefined)\" for references to inline elements
"Collapse All" and "Expand All" missing translations in Italian phrase table
Custom port value for an FTP publishing target is not saved
Source Control Get Latest or Checkouts performed externally whilst a project was open could result in subsequent changes being overwritten
Missing Summary content item type in toolbar / Menu Strip for COM Project
Editing a database column summary in a content file (database column) does not always immediately mark the content file as dirty (save button disabled)
New Topics don't get added to the Topic Category that is selected on the Project Explorer
Added a more useful error message if the Microsoft Help Viewer signing process fails (usually caused by lack of internet connectivity)
Build error when building a project with a widget property containing an empty name property
This update contains fixes for issues resolved since update 15.2.28.
This update contains fixes for issues resolved since update 15.2.27.
This update contains fixes for issues resolved since initial release.
Integration with cloud based discussion/community services (Disqus/Facebook/Solidopinion/Livefyre)
It is now possible to enable Community Features in the generated output using one of several third party cloud based Community/Discussion services. Community Features allow you to create a community around the content that you author with Document! X and HelpStudio by allowing your end users to post feedback and threaded comments. Integrating with the established best of breed Community/Discussion services in this way enables you to choose the service that makes the most sense for your particular scenario. Community Features are enabled using the Community Features page in the Project Profile Editor, are supported throughout the standard templates and are visible when you are authoring.
The name of the browser help root page (default webframe.html) can now be customized in the Build Profile Editor
Added a checkbox to COM Components and Assemblies in the Project Explorer to exclude/include all child items
Enhanced short filename generation options including saving mappings between builds, prefix replace and regex find and replace
Additional Short filename generation options have been added to Project Settings to enhance this important area of functionality. It is now possible to save the generated filenames between builds so that the same filename will always be generated for a given item. There are also additional options to shorten / transform the default generated filenames using a regular expression find and replace, or by removing a common file prefix. Shortening can now also be restricted to those filenames that would otherwise exceed a particular length (e.g. the windows path and filename length limitation of 260).
Added information to the online help on how to link to locally installed Microsoft Help Viewer content in Visual Studio 2012 and 2013
Added 2 new Table of Contents node types that automatically populate the ToC based on Topic Category/Topics
The new \"All Topics Categories\" Table of Contents node will automatically generate a Table of Contents structure at build time based on the Topic Category / Topic structure on the Project Explorer. A new \"Topic Category\" node type will do the same but just for a specific Topic Category. These new node types will save time and effort in arranging the Table of Contents if your Project Explorer already reflects the structure you would like to see on the Table of Contents.
New Option to automatically include a link to view Browser Help content with navigation tools when a content page is opened directly
A new 'Include a View with Navigation Tools link if a content page is opened without Browser Help Navigation Tools' option has been added to the 'Browser Help' page in the Build Profile editor. This new option will cause generated content pages to automatically show a link in the page header that will navigate to the same page but with full navigation tools (i.e. webframe.html#pagename.html) if the content page is opened directly. This is particularly useful for public content that is indexed by search engines - as users will often navigate from search results to the content page without the navigation tools.
Added a new 'Document! X Placeholder (for specific item)' ToC node type to include generated nodes only for a specific item
Although a fully automatic Table of Contents containing nodes for all of the items in your documentation project is a huge time saver for reference documentation items, there are times where you might want to divide up the ToC in a more specific way. For example, you might want to include the nodes for a specific assembly or namespace under the a part of the ToC that contains the conceptual topics (introductions, tutorials) that relate to it. This new ToC node type allows you to do that - the portion of the ToC generated for a specific item can thereby be placed anywhere on the ToC. The nodes that are automatically generated for the item can also be customized if required, in the same way as the regular Document! X placeholder node.
Visual Studio 2015 and Microsoft Help Viewer 2.2 Support
Integration with Visual Studio 2015, including the Visual Comment Editor for C#, VB and C++/CLI. Support for the new Microsoft Help Viewer 2.2 that ships with Visual Studio 2015 including deployment help information and generated batch files to illustrate how to deploy help for integration with Microsoft Help Viewer 2.2 in Visual Studio 2015.
It is now possible to check / uncheck multiple selected items on the Project Explorer
With multiple checkable items selected (using Ctrl+Click or Shift+Click), pressing the spacebar will check / uncheck all of the selected items.
Added context menu items to the Assembly root node, assembly and namespace nodes on the Project Explorer to deselect non public types
These new commands make it easier to ensure that all non public types are excluded on the Project Explorer. Note that there are also existing options on the .NET Filtering page in the Build Profile Editor to never include non public types in generated output.
Added Sort command to Project Explorer context menu for the Topics node to sort Topic Categories
The command is visible if the project or selected Topic Category contains > 1 Topic Category. This command makes it easier to keep large Topic Category lists organized.
Added Sort command to the Project Explorer Assemblies, XSD Schemas, Web Services and Databases nodes
The command is visible if the project contains > 1 Assembly/Xsd Schema/Web Service/Database. This command makes it easier to keep the Project Explorer organized for very large projects.
Document! X and HelpStudio now support Windows 10 (32bit and 64bit) as an installation platform
A prompt to automatically reload the project will be shown after a referenced file is changed
This change makes it easier to ensure you are always documenting from the latest version of an Assembly, Web Service file, Xsd Schema or COM Component. If your project includes one or more of those items, Document! X will automatically prompt you if the file has changed (i.e. a new version is copied over or you rebuild the component/assembly from Visual Studio). If you answer Yes to the reload prompt, Document! X will automatically reload the project (or restart the application and reload the project for .NET assemblies) in order to pick up the latest version. You will be prompted to save changes before the project is reloaded.
Added Sort command to the Project Explorer Content Files Context Menu
The command is visible if a project contains > 1 Content File. This command makes it easier to keep large Content File lists organized.
Execute external programs/scripts or show messages when building a saved Build Configuration
Build Configuration Event Actions allow you to define actions you want to perform when building a particular saved Build Configuration. Actions can be executed before or after the Build or Publishing operations. Actions can invoke an external program or script, or show/log a custom build message.
Microsoft Team Foundation Server 2015 Support
Support for Team Foundation Support and connecting to Team Foundation Server 2012-2015 from a machine with only Visual Studio 2015 installed.
Added a new rule kind to allow filter of all items belonging to a particular documentation type
This new rule kind makes it easy to create filters in a Build Profile to include/exclude all items from specific documentation types. For example, in a project that contained .NET, COM and Database documentation items you could create a Build Profile that outputs everything apart from .NET documentation, or a Build Profile that only outputs database documentation. This rule kind can also be useful to create a \"Topics only\" Build Profile (by adding a rule to exclude all reference documentation types) in order to quickly build only conceptual Topic output (e.g. for review).
Updated docs to include deployment information for Microsoft Help Viewer