Acrolinx for Visual Studio Code - Version 1.1 (30 August 2018)
With this release, we’ve put together a heap of improvements for Acrolinx for Visual Studio Code. The Sidebar is now embedded in your editor, you get check selection, language support, and a load of new supported file types. Plus, you can get it all with one click from the Visual Studio Marketplace. Code, comment, check - try it out!
Acrolinx Sidebar Embedded in Visual Studio Code
The Acrolinx Sidebar used to run as a separate application outside of Visual Studio Code. This meant that the Sidebar easily got hidden behind other application windows, which was a hassle. Embedding the Sidebar in Visual Studio Code means you can move it within your editor as you like. Use the “editor regions” feature in Visual Studio Code to organize your workspace with the Sidebar.
Available from Visual Studio Marketplace
The latest version of Acrolinx for Visual Studio Code is available with one click directly from the Visual Studio Marketplace. It couldn’t be easier!
More File Type Support
You can now use Acrolinx to check content in a wider range of file types – not just TEXT and MARKDOWN, but also XML, HTML, JSON, Java Comments, Java Properties, and C++ Comments.
Check a Selection of Your Content
Ever felt like one particular part of your content needs more attention? With check selection, you can now select parts of your document for Acrolinx to check.
Sidebar Start Page Now Included in Installation
Acrolinx used to load the Sidebar start page from the cloud. Now, we’ve bundled the start page with Acrolinx for Visual Studio Code.
Application Logs in the Sidebar
Your logging information used to only be accessible from the browser console. Now, Acrolinx writes a separate log file that you can open from the Sidebar About page.
Automate Installation and Configuration from the Command Line
You can now automate and configure Acrolinx directly from the command line.
Predefine Acrolinx URL
As an administrator, you can set the default Acrolinx URL for your writers to connect to.
Acrolinx used to save the Acrolinx URL and the user's authentication information in the local storage of the browser that loads the Sidebar. Now, Acrolinx saves your settings in a JSON file (acrolinxStorage.json) in your application.
Sidebar Now Available in Your Preferred Language
If you've set your application language in Visual Studio Code to English, German, French, Japanese, or Swedish, then the Sidebar will also appear in this language. For all other languages, the Sidebar will appear in English.
Error Message Appeared Instead of Sidebar Loading
In previous versions, you might have noticed an error message appearing sometimes when you click the Acrolinx button to show the Sidebar. The message read "Error command 'extension.acrolinx.showSidebar' not found". Now that we’ve embedded the Sidebar directly inside Visual Studio Code, you shouldn’t see this message anymore.
Set CORS Property to Null
Even though Acrolinx for Visual Studio Code doesn’t require CORS, you still need to actively set the property to NULL.
We've developed and tested this version of Acrolinx with Visual Studio Code 1.25.1 on Windows, Mac OS X, and Linux.
This release requires the following Acrolinx products:
- Acrolinx server version 5.5 or later
Acrolinx for Visual Studio Code - Version 1.0.1 (19 June 2018)
This is an important service release to support Visual Studio Code Version 1.24.1.
Support for Visual Studio Code Version 1.24.1
Acrolinx stopped working, if you updated to the latest Microsoft Visual Studio Code version on Windows. The reason for this was a change in Visual Studio Code. The installation file paths were changed so the mapping to the Acrolinx extension was broken. We've fixed this to work around the issue in Visual Studio Code.
If you want to know how we did it, take a look at: https://github.com/Microsoft/vscode/issues/51387
Acrolinx for Visual Studio Code - Version 1.0 (14 February 2017)
We're pleased to announce Acrolinx for Visual Studio Code — our first extension for Visual Studio Code. Use Acrolinx for Visual Studio Code to check content in text or GitHub-flavored markdown format. For how to install the extension, see the article Acrolinx for Visual Studio Code in this help center.
Check GitHub-flavored Markdown and Text Files
You can use Acrolinx to check text (*.txt) and GitHub-flavored markdown (*.md) files. Acrolinx converts the markdown to HTML to analyze your content. If you use different flavors of markdown, you might see unexpected results. For an overview of the GitHub-flavored syntax, see this markdown cheatsheet or the official GitHub writing guidelines .
Manage Extraction Settings on the Acrolinx Server
For all Acrolinx Sidebar editions, you can configure the extraction settings in the Acrolinx Server . Your guidance package includes a default Context Segmentation Definition (CSD) file specific to markdown. You'll need to update to a new guidance package to get this new CSD.
Be sure to request a new license to get the Sidebar edition activated for your server.
Install Acrolinx From the Command Line and Preset the Address of the Acrolinx Server
We've packaged Acrolinx for Visual Studio Code as a standard .vsix extension. You can automate and configure Acrolinx for users just like you would for other Visual Studio Code extensions. For more details, see the article Acrolinx for Visual Studio Code in this help center.
Acrolinx for Visual Studio Code supports Microsoft Visual Studio Code version 1.7 and later. We've developed and tested this version of Acrolinx with Visual Studio Code 1.9 on Windows, Mac OS X, and Linux.
This release requires the following Acrolinx products:
- Acrolinx server version 5.2 or later
- Acrolinx guidance package version 5.2 or later
- Acrolinx sidebar version 14.3 or later.
Sometimes a Sidebar Card Appears Deactivated for Text
In some circumstances, your sidebar card appears deactivated when you click on it. For example, if an issue occurs in mouse-over text or across a single line break.
You might see a false issue such as a grammar issue appear even though your content is correct. We're working on fixing this for the next release.