Visual Assist build 2210 is available

After a long hiatus between builds, the first of year 2017 is now available. Visual Assist build 2210 include two big improvements: support for Visual Studio 2017 and Code Inspection.

Visual Assist build 2210 supports the release version of Visual Studio 2017. If you used Visual Assist in a release candidate of the IDE, please upgrade to build 2210.

Code Inspection is a new feature in Visual Assist that analyzes code quality as you edit. The feature, based on LLVM/Clang, warns you of code issues and if possible, suggests and applies quick fixes. The first set of code inspections, corresponding to a subset of clang-tidy checkers, offers to modernize C++ to the extents supported by your project toolsets.

Code Inspection is a beta feature so it is disabled by default. To try the feature, begin by enabling it in the options dialog for Visual Assist.

Code issues resulting from inspection are underlined in the text editor. To understand an issue, hover over its underlined text.

If the underline is solid, see a quick fix by moving the caret to it and opening the Quick Actions and Refactorings menu (Shift+Alt+Q).

To browse all code issues for the current file, open the Code Inspection tool window found in VAssistX | Tools.

Before we introduce more code inspections, we want your feedback on the feature’s functionality, performance, and UI. Please send your comments to support@wholetomato.com or share them in our community forums.

Visual Assist build 2210 also improves support for several Unreal Engine 4 keywords, finds an include path in the CppProperties.json of a folder-based C++ project, and fixes several bugs.

Visual Assist build 2210 requires software maintenance through 2017.03.08.

Check out the complete list of what’s new in build 2210, learn more about Code Inspection, or download the installer.

2 thoughts on “Visual Assist build 2210 is available

    • Excellent question. I answered it a few days ago but subsequently realized build 2210’s support of Unreal Engine is badly flawed. Setting EnableUC to 01 does enable support for UE4 keywords, but it also causes Visual Assist to find and parse keywords specific to Unrealscript / UE3.

      If you use Visual Assist with UE4, exit your IDEs and delete EnableUC from the registry. Wait for the next build of Visual Assist. We will separate support for UE3 and UE4.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s