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.