Follow us on Twitter

Atomineer Pro Documentation Development Summary

This extension began development in 1996 (for Visual C++ 4.0), and has been evolving and improving through constant use by software professionals ever since. More recent developments are listed below...

  Visual Studio Partner  

September 2018

  • More work on extension initialisation to best support changes in Visual Studio startup.
  • Improved C++ parsing to address an issue with access modifier prefixes on the same line as a member declaration.
  • Fixed an issue with code element identification and indentation when parsing member variables preceded by attributes on the same line.

July 2018

  • Under-the-bonnet changes and testing to ensure Atomineer Pro Documentation is compatible with some changes that are coming in Visual Studio 2017 (15.8) and future versions, and testing of these changes in older versions.
  • Updates to Atomineer Spelling for similar forwards compatibility issues.
  • Improvements in Atomineer Spelling's word detection, and a fix for a regression that caused symbols with underscores to be handled as if they were separate words.
  • Fixed an issue in Delete Documentation which could cause single-line comments to not be deleted for some comment block configurations.
  • Fixed a parser categorisation issue that caused incorrect documentation to be generated for some enum entries.

May 2018

  • Updated Atomineer for Atmel Studio 7.0
  • Improvements to the Align Code Into Columns behaviour for C# 7.0 syntax
  • Tested against Visual Studio 15.7 release and 15.8 prerelease builds

April 2018

  • Improvements to text formatting within the Doc Editor view, with better handling of tall narrow aspect layouts and ne template settings for controlling maximum column widths.
  • Improved handling of embedded XML/HTML elements within the Doc Editor
  • Fixed a parsing error that could cause multi-line C++/C# declarations to be incorrectly classified as enum entries
  • Added support for documenting within .cshtml files
  • Addressed a report of unknown failures in Extensions. We could not confirm an actual problem in Atomineer, but have added more exception checks to minimise the risk that Atomineer might cause such reports from Visual Studio.
  • Some changes to our website for renewals, and our company policy information has been updated in light of the introduction of GDPR across Europe.

March 2018

  • Improvements to Typescript/Javascript support. As there is a loit of variation in the syntax of these languages, if you spot anything that Atomineer doesn't handle well, please let us know so we can ensure it's fully supported.
  • More work on Atomineer Spelling, as recent updates (presumably .net/roslyn) have also retroactively affected older Visual Studio installs, causing the 2015 Spelling to cease working. We have now back-ported the fixes that were required for VS2017 into the previous version and tested in VS 2013 and 2015. The new implementation no longer requires roslyn/intellisense to operate, so also works on non-compiling code.
  • Spelling 2017: Fixed an issue that caused spelling corrections to be suggested occasionally on text outside of doc comments. The new implementation no longer requires roslyn/intellisense to operate, so also works on non-compiling code.
  • Spelling: Improvements to default custom dictionary.
  • Fixed a small bug in the new declaration parser that caused problems for enum members using UPPER_CASE naming style.
  • Internal: improved reporting mechansim for errors and notifications.

February 2018

  • Rewrote the Atomineer Spelling extension to resolve issues in Visual Studio 2017. Several recent changes to the Roslyn engine and some other internals of Visual Studio caused problems with the installer and then the spelling highlighting. In addition, switched the suggestions menu over to use the new Visual Studio 'lightbulb' suggestion system.
  • Improved handling of enum members in the new declaration parser implementation.
  • Improvements to parsing relating to some old C style syntax cases.
  • Fixed an edge case in handling of templated classes
  • Adjusted 'asSee' generated crefs to use double rather than single quotes.
  • Fixed an issue caused by a software update on our web host, which affected some non-essential featues on the account management web page (such as the last downloaded version not being reported correctly).

January 2018

  • Added handling for C-style structs, unions and enums (as in: struct S function() {}).
  • Documentation Editor Improvements
    • Added a new "Add Entry" button. This allows optional entries (e.g. remarks) to be inserted into the documnetation.
    • You can now navigate to the Next/Previous code element using Alt+Down and Alt+Up. (The Alt key binding is used to avoid clashes with Visual Studio's built in bindings)
    • Next/Previous navigation now places the input focus in the first editable field so that you can now fully document an entire file through the editor without needing to use the mouse.
    • Some other small improvements.
  • Fixed a regression in live typing aids that could extend a comment incorrectly if return was pressed on the final line of a /* */ comment.

December 2017

  • Tested with Visual Studio 2017 (15.5). We recommend users of Atomineer Spelling update to this version of VS 2017 as it resolves issues with the underlining highlights for misspelled words.
  • Added <paramref> support to the documentation editor. New paramrefs can be added from the context menu on any editable field. Existing paramrefs are shown as the parameter name with a highlighted background colour - just click the parameter name to change the reference.
  • Improved parsing of typescript declarations, fixing a case that was handled incorrectly
  • Fixed a rare edge case where Atomineer was not detecting doc comments in single-line /* ... */ comments, causing duplicate comments to be added.

November 2017

  • Added support for C# 7 expression-bodied members in the new method declaration parser, which was unfortunately missed due to some unit tests not being applied to the new code.

October 2017

  • Rewrote the method declaration parser to fully handle inline syntax in C++ and C# declarations, as there were edge cases that the previous parser did not handle correctly.
  • Documentation editor: Improved bullet-list support.
  • Fixed a parsing glitch in Natural Docs exception entries.
  • A large behind the scenes upgrade to our website.

September 2017

  • Documentation editor now has next/previous buttons. These advance the cursor to the next/previous code element and if necessry, executes Add Doc Comment to create a comment, which can then be adjusted in the editor. This allows you to easily step through a file and document it directly in the editor.
  • Documentation editor: Added simple bullet-list support.
  • Documentation editor now automatically snaps its toolbar to the top or left side of the view
  • Documentation editor: some general improvements and under-the-bonnet work to support planned future features.
  • Fixed an issue that could sometimes stop the new template system's EntrySettings being correctly applied. This could cause several symptoms (e.g. optional entries such as seealso being incorrectly deleted from comments while updating them, punctuation being applied to entries that should have had the feature disabled).
  • Added an option for Doxygen-style comments to place in/out specifiers before or after the parameter name.
  • Improved C# 7.0 support for expression-bodied properties and added support for tuple parameters.
  • Fixed a small bug in the preferences app relaing to the 'enforce blanks' settings which worked correctly, but were not being displayed properly when reopening the preferences.
  • Fixed: Word wrapping engine could sometimes break URLs containing minus characters.
  • Improved parsing of C# generics
  • Added support for C++11 brace-initialisation syntax.
  • 'Reformat Doc Comment' will no longer duplicate documentation for parameters.
  • Some more support for projects
  • Small tweaks to the installer to support VS2017 better.

July 2017

  • For Visual Studio 2017/2015, the Documentation Viewer has been upgraded to a Documentation Editor. Edits made in this view will be written back to your source code automatically when the input focus moves out of any entry (i.e. if you switch to editing a different entry, or move the input focus back to your source code, or to another application). The editor supports some basic markup (<b> <i> <code> ) and has been tested primarily with XML documentation; it is being relessed now as a beta feature so that more users can feed back to us if they find any issues with the many variations of documentation styles and formats in the wild, to allow us to develop the feature forwards more quickly. Please note that the editor does not currently support a full set of markup features - markup such as inheritdoc, see, paramref, bullet lists and tables, as well as special doxygen markup (@ commands) will be supported in upcoming releases.
  • Resolved a regression in reformatting of indentation (a poor interaction with specific formatting options), which was introduced by an attempted fix for code block indentation in the 9.34 release. The fix was rolled back and a new fix implemented which does not introduce any side effects.
  • Added a new 'Reformat Doc Comment' command. This reformats a doc comment exactly as Add/Update Doc Comment does, but without adding any new entries to it.
  • The 'convert to entities' option has been expanded, so that < > & can be converted to XML entities &lt; &gt; & or now into more human readable { } + characters.
  • Further small improvements to the C# 7.0 parser.
  • Fixed an edge-case which could adversely affect parsing of attributes embedded within method parameter lists.
  • Fixed a minor parsing issue that was caused by unrecognised macros with 1-character names applied after parameter declarations.
  • Fixed an issue in Doc All in File where some code constructs were not correctly located when intellisense was unavailable, resulting in failure to document some code elements.
  • Fixed a small bug in the preferences that meant generation of 'inheritdoc' rather than 'seealso' was not persisted and had to be set manually.
  • Fixed an issue in the new template system that caused DocXml settings to be applied to Doxygen entries when they used a custom tag name.

Older versions

Details of versions from 2009 to this date are archived here

Copyright © 1996-2018 Atomineer. All Rights Reserved. Any trademarks reproduced in this text are the property of their respective owners - Contact us - Company Info