Visual Assist build 2116 introduces preliminary support for Visual Studio 2017 RC.
Testing of Visual Assist with Visual Studio 2017 RC is ongoing.
The Visual Assist suggestion and completion listbox features are available in VS2017RC, however they are not complete. Development is continuing.
The Visual Assist .exe installer erroneously reports an install failure when using a localized (non-English) version of Visual Studio 2017. This will be fixed in the next release of Visual Assist. [Fixed in VA build 2118.]
Folder-based solutions aren't working quite as well in the RC than in earlier Preview releases. The system include paths aren't being populated properly. After you open a folder, check to see if the "stable include files" list on the C/C++ Directories page of the VA Options dialog is reasonable. You may have to switch Platform from Win32 to Custom and manually add system include paths to the list. [The situation has improved in the post-RC update of VS2017; unrelated to that update, folder-based solutions will see improved support in the next VA release.]
All Visual Assist installers are incompatible with RC 3. Running any VA installer after RC3 has been installed (or updated from a previous RC) results in a setup error.
If you already had Visual Assist installed in a previous RC, it will still be installed after updating VS to RC 3.
"Faster Project Load" of projects created in earlier versions of Visual Studio that have not been retargeted for Visual Studio 2017 are incompatible with Visual Assist. When build of these projects is attempted, various strange cast errors are reported by VS.
If you encounter these errors, set Faster Project Load to false at: Tools | Options | Text Editor | C/C++ | Experimental Restart Visual Studio after changing the value.
The source of the problem has been identified by Microsoft and a fix is expected to be in the first update to Visual Studio 2017 after RTW.
In the meantime, we are investigating the problem from the Visual Assist side.