Privacy Policy Updated

We updated our privacy policy per the EU’s General Data Protection Regulations (“GDPR”) which went into effect today, May 25th, 2018. While the GDPR is a European law, we clarified and applied our privacy policy to everyone, independent of location.

Our updated privacy policy is more specific with regard to the information we collect, how we use the information, how we share the information, and your rights to the information.

If you visit www.wholetomato.com or forums.wholetomato.com on or after May 25, 2018, you are agreeing to the terms of our updated privacy policy.

You do not need to take any action.

Visual Assist build 2270 is available

Exhibiting at the Game Developer Conference (GDC) in March gave us the rare opportunity to interact—face to face—with a lot of Visual Assist users. Those who visited our booth picked up tips and swag, and left behind terrific feedback. The interactions gave us a better understanding of how Visual Assist is used, and how we could improve an already great product. A few of the improvements are included in Visual Assist build 2270, which is now available.

Source Links, introduced last June, was upgraded in build 2270 to support previewing of files whose paths appear in source comments. When Source Links and its File Viewer plug-in are enabled, hover over a path to see a preview of the file’s content. Preview-able formats include HTML, XAML, RTF, text, and image formats such as png and jpg.

Right+Click any path for file-related options.

Find References (Shift+Alt+F) has always been faster and more feature-rich than the built-in equivalent. In build 2270, the feature’s dialog was tweaked to indicate the effect of the filtering toggles D, S, R, and M.

Right+Click in a results window for toggle meanings.

Build 2270 continues our suite of improvements for users of Unreal Engine 4 (UE4). In addition to better parsing and coloring, settings related to UE4 are now easily accessed on a new page in the options dialog of Visual Assist.

Finally, Code Inspection was moved out-of-process to reduce the memory footprint of Visual Assist, thereby reducing the likelihood of an out-of-memory crash of Visual Studio.

Build 2270 requires software maintenance through 2018.04.30.

Check out the complete list of what’s new in build 2270, enable the File Viewer plug-in for Source Links, learn to filter results of Find References, or download the installer.

Visit us at GDC 2018 in San Francisco

Whole Tomato Software will exhibit at the Game Developer Conference this week, March 21-23, in San Francisco. If you attend the expo, stop by booth 123 to see the latest features in Visual Assist, share your wishes for the product, and pick up some nifty swag.

Visual Assist build 2258 is available

Visual Assist build 2258 is the first of the new calendar year and evidence of a return to normalcy at Whole Tomato. Last year’s dealing with bugs in the Fall Creators Update was an unwelcome distraction.

Long-time users of Visual Assist know that Open File in Solution (OFIS) has been a mainstay of Visual Assist since the product’s inception. Yet, there seems always room for improvement in the feature. With build 2258, the OFIS dialog now accepts target character positions when specified with a line number. The improvement better accommodates copying of diagnostic locations from build logs directly into the dialog.

OFIS (Shift+Alt+O) also recognizes when the current solution is in one of many directories under a git root, and expands the domain of searchable files to all files under the root—not just those within the current solution. Use the Ctrl+D toggle in the dialog to show/hide the relevant files.

For those who set bookmarks or manage to-do’s using VA Hashtags, you can now navigate the tool window of hashtags even though focus is in the edit field. Use Up-, Down-, Left-, and Right-Arrow to navigate nodes, and Enter to open/close or jump to a location.

Also with build 2258, game developers with Unreal Engine 4 (UE4) get better parsing, italics for local engine installations, smarter Create Implementation, and enabling of support for UE4 via the options dialog of Visual Assist.

Build 2258.5, with its bug fix for the options dialog, requires software maintenance through 2018.03.06.

Build 2258 requires software maintenance through 2018.02.20.

Check out the complete list of what’s new in build 2258; learn about character position in OFIS, hashtags navigation, or support for UE4; or dispense with more reading and download the installer for build 2258.5.

Visual Assist build 2248 is available

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.

December 12th update resolves another Visual Studio crash

If you follow news from Whole Tomato, you know that Microsoft released several builds of Windows 10 with bugs that caused Visual Studio to crash when Visual Assist was installed. More recently, Microsoft introduced a change in Visual Studio 2017 15.5 that causes the Code Inspection feature of Visual Assist to crash.

If you use Visual Studio 2017 and updated to 15.5, disable Code Inspection in the options dialog of Visual Assist. The next build of Visual Assist will include a fix that will let you re-enable the feature.

If you run Windows 10 Version 1709 (Fall Creators Update), your installation of Windows 10 must be up to date in order to use Visual Assist. Microsoft’s December 12th update to OS Build 16299.125 includes a required fix for a CreateWindowEx() failure.

If you run Windows 10 Version 1703 and deferred installation of the Fall Creators Update, you are free to un-pause Windows Update and upgrade to 1709.

If you prefer to remain with Windows 10 Version 1703, you must run at least OS Build 15063.729, released November 22nd, in order to have a required fix for a broken hook mechanism.

Thank you for your patience as we grapple with the bugs and crashes.

If all goes well, the next post in this blog will simply announce a new build of Visual Assist.

Speed up opening of editors when using Visual Assist in Windows 10 (Fall Creators Update)

Microsoft tightened security in the Windows 10 Version 1709 Fall Creators Update (FCU), but unfortunately, the tightening adversely affects the performance of applications that use the Win32 GetPixel API. Visual Assist is one such application so initial opening of editor windows in Visual Studio, when Visual Assist is active, can be extremely slow.

You can speed up the opening of edtor windows when using Visual Assist to pre-FCU levels by disabling Control Flow Guard for Visual Studio. Navigate to:

Windows Defender Security Center | App & browser control | Exploit protection settings | Program settings | Add program to customize | Add by program name

Be cautious and choose the exact file path(s) for Visual Studio, or disable protection for any application named “devenv.exe”.

Scroll to disable Control Flow Guard (CFG).

You might improve the performance other aspects of Visual Assist in Visual Studio, at least with respect to the effects of tighter security in the FCU, by disabling all 21 program security settings specific to the application.

Apply, and restart your PC.

You can improve performance of all affected applications in the FCU by disabling CFG at the system level:

App & browser control | Exploit protection settings | System Settings

Obviously, disabling a security feature has its own cost, i.e. less security. You can learn more about the slowness of the API at TenForums and in the Visual Studio Developer Community.