Visual Assist build 2248 closes our dealing with recent bugs in Windows 10 and a problem with Visual Studio 2017. Prior posts in this blog describe the bugs and the workarounds, but the outcome of the ordeal is that if you use Windows 10—version 1703 or 1709—update to the latest build from Microsoft. And if you use Visual Studio 2017, update to build 15.5 of the IDE. Visual Assist operates as expected with the updates.
Find References, a staple of Visual Assist for more than a decade, was improved in build 2219 such that results designate, and can be filtered on, class creation/construction hits. Build 2248 extends the hits to include calls to CreateInstance and CoCreateInstance. Toggle the hits by pressing ‘c’ in a result window; see only the hits with the ‘d’, ‘r’, and ‘s’ toggles.
Code Inspection continues to mature in build 2248 with three new quality checks, all of which can be quick fixed:
- Range-based loop variable can be a const reference
- Local variable can be a const reference
- Prefer transparent functor
With build 2248, game developers who use Unreal Engine 4 (UE4) get specifier completion for the UCLASS(), USTRUCT(), UFUNCTION(), and UPROPERTY() macros. If you develop with the engine, be sure to set the registry to make Visual Assist compatible with UE4. The registry setting enables the specifier completion as well as other UE4-specific behavior.
Build 2248 requires software maintenance through 2017.12.16.
Check out the complete list of what’s new in build 2248, learn about toggling within Find References, or download the installer.
