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.
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.
Two bugs in recent updates to Microsoft Windows 10 cause Visual Studio to crash when certain extensions, including Visual Assist, are installed. Microsoft fixed one of the bugs, a broken hook mechanism, in its November 14, 2017, update.
All Windows 10 users with Visual Assist should install the November 14 update, available via Windows Update or via stand-alone packages. Download the stand-alone update from the Windows Update Catalog, accessed from the bottom of the description of the update for Windows 10 Version 1703 or update for Windows 10 Version 1709 Fall Creators Update.
Microsoft acknowledged that the second bug, which causes CreateWindowEx() to fail, exists in Windows 10 (64-bit) Fall Creators Update (Version 1709). The CreateWindowEx bug also causes Visual Studio to crash when Visual Assist is installed. The workaround recommended by Microsoft and by Whole Tomato is to rollback to the previous version of Windows 10. If you do rollback, defer installation of the Fall Creators Update and install the November 14th update.
If you run Windows 10 (64-bit) Fall Creators Update (Version 1709) and you cannot rollback, install Visual Assist build 2238 to mitigate the CreateWindowEx() failures. If Visual Studio continues to crash, disable Visual Assist and wait for another update from Microsoft, mid-December at earliest, before resuming normal use of Visual Assist.
Thank you for your patience as we work around these Windows bugs.
Stay tuned for our next announcement.
The Windows 10 Fall Creators Update (FCU) 1709 contains a bug that causes CreateWindow() and CreateWindowEx() to fail unpredictably. The bug prevents Visual Assist from rendering all components of its UI, and eventually causes Visual Studio to crash.
Microsoft has acknowledged the CreateWindow() bug and is investigating its cause, but the bug will not be fixed—at the earliest—until the December Patch Tuesday. If you want to use Visual Assist until Microsoft releases a fix, defer installation of the Windows 10 Fall Creators Update.
Separately, Microsoft broke Windows hook procedures in Windows 10 Build 15063.608, issued Sept 12th. The hook bug causes Visual Studio to crash intermittently, e.g. when opening certain dialogs of Visual Assist. Microsoft has acknowledged the bug and is scheduled to release a fix on November Patch Tuesday.
Stay tuned for our next announcement regarding the bugs.
Several bugs in recent updates to Microsoft Windows 10 cause Visual Studio to crash when certain extensions, including Visual Assist, are installed:
- Windows 10 Build 15063.608, issued Sept 12th, broke Windows hook procedures located in high memory.
- Windows Version 1709 (Fall Creators Update), released Oct 17th, broke also CreateWindow() and CreateWindowEx().
Microsoft is actively seeking resolutions. Fixes should be released on a Patch Tuesday.
If you run Windows 10, and:
- You want to try Visual Assist, wait for the problems to be resolved before starting your trial.
- You use Visual Assist, you have not yet installed the Fall Creators Update, and:
- Visual Studio crashes when you open dialogs of Visual Assist, disable Visual Assist. You are likely suffering from the broken hook mechanism.
- Visual Studio does not crash, keep your version of Windows, i.e. delay installation of the Fall Creators Update.
- You use Visual Assist, you installed the Fall Creators Update, and components of the Visual Assist UI fail or Visual Studio crashes, disable Visual Assist or try rolling back to the previous version of Windows. You are likely suffering from CreateWindow() failures.
Stay tuned for our next announcement regarding the recent Windows 10 updates.
The Tomato will exhibit at the Game Developer Conference next week, March 1-3, in San Francisco. If you will attend the show, be sure to stop by booth 2438 and say hello. Get a peek at new and forthcoming features in Visual Assist, share with us your wish list, and introduce Visual Assist to your coworkers. We will have swag on hand.
Microsoft announced today the Preview 5 release of Visual Studio “15”. The Visual C++ Project Engine changed between Preview 4 and 5, and the change prevents Visual Assist from loading solutions. The developers at Whole Tomato Software are working on a resolution.
If you use Visual Assist in Visual Studio “15”, stay with the Preview you have or update and wait for our next build. The next build of Visual Assist will add support for Preview 5 and nothing else.
Stay tuned to the usual channels.