We are delighted to announce the release of Document! X and HelpStudio 2015.2. This update includes Visual Studio and Team Foundation Server 2015 Support, Microsoft Help Viewer 2.2 Support, Compatibility with Windows 10, Community Integration (Disqus, Facebook etc.) amongst a range of other features and fixes.
If you have a current subscription license or purchased on or after 22nd June 2015, the upgrade to 2015.2 is free. If you don’t have an active subscription and purchased 2015.1 before 22nd June 2015, or you have a 2012, 2013 or 2014 license, a discounted upgrade is available at http://www.innovasys.com/store
You can find more information on how to upgrade to 2015.2 in the full release note:
Document! X 2015.2 Release Note:
HelpStudio 2015.2 Release Note:
Document! X and HelpStudio Bundle 2015.2 Release Note:
What’s New in 2015.2
Visual Studio 2015 Integration
Integration with Visual Studio 2015, including the Visual Comment Editor available for C#, VB and C++/CLI code files.
Microsoft Help Viewer 2.2 Support
Support for Microsoft Help Viewer 2.2, the updated version of Microsoft Help Viewer included with Visual Studio 2015. Output that targets Microsoft Help Viewer will now automatically register with Microsoft Help Viewer 2.2 if it is installed locally, a link to view the generated output will be included in the Build Results and batch files will be generated with the commands necessary to deploy help to Microsoft Help Viewer 2.2 on other machines.
Team Foundation Server 2015 Support
Support for Microsoft Team Foundation Server 2015 for Source Control integration.
Windows 10 Support
Full support for use on the new Windows 10 operating system.
Integration with cloud based discussion/community services (Disqus/Facebook/Solidopinion/Livefyre)
It is now possible to enable Discussion/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.
Enhanced shortened filename generation options
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).
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.
Custom Build Configuration Event Actions
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.
Document! X Placeholder for a specific item Table of Contents Node
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.
New filtering rule 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).