Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 Solution reload in VS2017 isn't updating VAX
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

MrDoomMaster
Tomato Guru

251 Posts

Posted - Jun 08 2017 :  4:11:23 PM  Show Profile  Reply with Quote
I am using CMake + Visual Studio 2017 for C++ projects. My normal workflow with CMake is as follows:

1. Generate respective Visual Studio 2017 Solutions & Projects using CMake 3.8+
2. Open the generated SLN file
3. Allow VAX to scan the solution and projects, wait for it to finish
4. VAX "Open File in Solution" shows all files as expected.
5. Go to CMakeLists.txt script, add a new source file (In the screenshot this is "TestCollisionManager.cpp")
6. Click "Generate" in cmake-gui.exe to re-generate the solution & projects
7. Switch back over to the running VS2017 instance and click "Reload All" when prompted to reload the solution and/or projects
8. Wait for solution to reload, projects to initialize, and VAX to finish parsing.
9. Invoke "Open File in Solution" and enter a substring that should match the new file added in step 5.
10. Notice that the file does not show in the result list.

Screenshot of the issue is below. Notice that the new file (named "TestCollisionManager.cpp") properly shows up in the Solution Explorer, however it does not show up in the VAX "Open File in Solution" list of results.

Workaround is to close the solution then open it again. This causes the file to now show up in OFIS.



VAX version information:

VA_X.dll file version 10.9.2217.0 built 2017.04.26
DevEnv.exe version 15.0.26430.12 Professional
msenv.dll version 15.0.26430.4
Comctl32.dll version 6.10.14393.447
Windows 10 10.0 Build 14393
8 processors (x86-64, WOW64)
Language info: 1252, 0x409

Platform: Project defined
Stable Includes:
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.2\Include\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\um;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\UnitTest\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.14393.0\ucrt;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\include;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\atlmfc\include;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\include;

Other Includes:

Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.14393.0\ucrt;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\src;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\crt\src;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\atlmfc\src\atl;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\atlmfc\src\mfcm;
E:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.10.25017\atlmfc\src\mfc;

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jun 08 2017 :  4:26:30 PM  Show Profile  Reply with Quote
This will be addressed in the next release of VA (due next week), but only in VS2017 15.3. There is a bug in 15.0, 15.1 and 15.2 such that if VA listens for solution change events, then compilation is broken in some circumstances; in order to not break compilation, VA does not listen for those solution events in VS2017. The bug is fixed for 15.3 (confirmed in the current preview release), so in that version VA is able to again subscribe to solution change events.

Edited by - sean on Jun 08 2017 4:27:58 PM
Go to Top of Page

MrDoomMaster
Tomato Guru

251 Posts

Posted - Jun 08 2017 :  4:39:43 PM  Show Profile  Reply with Quote
Thanks for the info Sean. Any idea when 15.3 will be made available? I wasn't able to find anything about it.

Supposedly they're upgrading the built-in CMake to 3.8 with 15.3 as well.
Go to Top of Page

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jun 08 2017 :  6:16:59 PM  Show Profile  Reply with Quote
15.3 is the current Visual Studio 2017 Preview and can be downloaded from https://www.visualstudio.com/vs/preview/

I suspect it will graduate to non-preview within the next month -- but that is just an opinion.

You can install it side-by-side with the non-preview version of VS2017.
Go to Top of Page

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jun 16 2017 :  8:53:07 PM  Show Profile  Reply with Quote
This was case=104119.
case=104119 is fixed in build 2219 but only for 15.3.
Go to Top of Page

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jun 19 2017 :  2:48:11 PM  Show Profile  Reply with Quote
The fix for 104119 is bad and likely breaks compilation of some solutions in some earlier versions of vs2017. We'll have an update this week.

Edited by - sean on Jun 19 2017 2:49:35 PM
Go to Top of Page

sean
Whole Tomato Software

USA
2817 Posts

Posted - Jun 22 2017 :  5:47:48 PM  Show Profile  Reply with Quote
Build 2223 restores behavior to that of build 2217, which for this thread means that solution reload is again required after projects are modified.

However, there is a new registry value named ForceVs2017ProjectSync that you can use to force VA to monitor the solution events. The value defaults to off/00 to prevent compilation failures in some cases. You can force the old pre-VS2017 behavior by setting ForceVs2017ProjectSync to 01. If during compilation of C++ projects, you encounter 'Specified cast is not valid' errors, then restore the value to 00.

Once VS2017 15.3 is out of preview, I hope that 15.2 will not receive any more updates and we'll be able to use minimum version info to determine if a fix is present in VS.

Edited by - sean on Jun 22 2017 5:48:19 PM
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000