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. 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. This will be addressed in the next release of VA (due next week), but only in VS2017 15.3. 0 built 2017.04.26Ĭ:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.2\Include\um Ĭ:\Program Files (x86)\Windows Kits\10\Include\3.0\winrt Ĭ:\Program Files (x86)\Windows Kits\10\Include\3.0\shared Ĭ:\Program Files (x86)\Windows Kits\10\Include\3.0\um Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\UnitTest\include Ĭ:\Program Files (x86)\Windows Kits\10\Include\3.0\ucrt Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\include Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\7\atlmfc\include Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\7\include Ĭ:\Program Files (x86)\Windows Kits\10\Source\3.0\ucrt Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\src Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\7\crt\src Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\7\atlmfc\src\atl Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\7\atlmfc\src\mfcm Į:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\7\atlmfc\src\mfc This causes the file to now show up in OFIS. Workaround is to close the solution then open it again. 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. Notice that the file does not show in the result list. Invoke "Open File in Solution" and enter a substring that should match the new file added in step 5.ġ0. Wait for solution to reload, projects to initialize, and VAX to finish parsing.ĩ. Switch back over to the running VS2017 instance and click "Reload All" when prompted to reload the solution and/or projectsĨ. Click "Generate" in cmake-gui.exe to re-generate the solution & projectsħ. Go to CMakeLists.txt script, add a new source file (In the screenshot this is "TestCollisionManager.cpp")Ħ. VAX "Open File in Solution" shows all files as expected.ĥ. Allow VAX to scan the solution and projects, wait for it to finishĤ. Generate respective Visual Studio 2017 Solutions & Projects using CMake 3.8+ģ. My normal workflow with CMake is as follows:ġ. I am using CMake + Visual Studio 2017 for C++ projects. Solution reload in VS2017 isn't updating VAX The SDF files on an SSD fixes the problem but should not be necessary.Whole Tomato Software Forums - Solution reload in VS2017 isn't updating VAX Random reads from it when changing between debug and release. The underlying cause is that the SDF file gets fragmented and,Īccording to xperf profiling I've done, VS will sometimes do 20,000+ After that it returns to normal again, for aboutĪ week, or so until you need to do it again. To fix it you need to close the solution and goĭelete the. Sometimes working with a big solution (mainly C++ projects) becomes The *.sdf file there contains the intellisense database- if you delete this files and reopen your project in visual studio, it rebuilds the cache.ĭeleting the sdf file solved the problem for me. Note that if you delete the whole folder you will lose your window layout configurations etc.įor previous versions, close Visual Studio and navigate to your project folder. It contains among other things the intellisense database (it should be possible to delete only the files specific to intellisense, if we knew which ones). vs folder in the same folder as the solution. For VS2015, 2017 and VS2019 close Visual Studio and delete the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |