Author |
Topic |
dswallow
New Member
USA
3 Posts |
Posted - Dec 13 2017 : 10:31:10 AM
|
quote: Originally posted by sean
VS2017 15.5 introduced some header changes that crash the Code Inspection parser. To prevent that particular crash, disable Code Inspection. A fix will be available at the end of the week.
Thanks; that seems to have helped. :) |
Doug Swallow
|
|
|
phillipfoose
Junior Member
USA
23 Posts |
Posted - Dec 13 2017 : 12:50:10 PM
|
The performance seems to be much better, and I haven't yet gotten any crashes (knock on wood), but have had the VA navigation bar disappear off and on... |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
|
sean
Whole Tomato Software
USA
2817 Posts |
|
phillipfoose
Junior Member
USA
23 Posts |
Posted - Dec 13 2017 : 1:30:16 PM
|
quote: Originally posted by sean
And also confirm that you have KB4054517 installed ( http://support.microsoft.com/kb/KB4054517 ).
Having trouble reproducing the missing window, I'll leave the logging on and if it repros I'll post the logs here. |
|
|
azur
Ketchup Master
Germany
59 Posts |
Posted - Dec 14 2017 : 06:59:10 AM
|
@sean: I have installed: KB4054517; VS 15.5.1 and VA 2238.2 but VisualStudio crash on the first action in the editor.
So I followed your hint "disable Code Inspection". After that I can use VisualStudio with VA.
Thanks
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Dec 18 2017 : 7:22:22 PM
|
case=112698 was opened for the Code Inspection crash that started with the 15.5 update. case=112698 is fixed in build 2248. |
|
|
Alexis
New Member
2 Posts |
Posted - Jan 06 2018 : 07:46:12 AM
|
Hi! I am currently having this problem, my last visual assit available version is 2237 I was reading that the problem should be fixed now with the lastest windows 10 updates. Is this correct?
My VA version should work just fine?
thanks and excuse my English
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jan 06 2018 : 08:59:53 AM
|
Please try installing all available Windows 10 updates, and see if this fixes the problem. We think it should, but most people testing this are using VA 2248, which has some changes to try and handle the problem on our side. |
zen is the art of being at one with the two'ness |
|
|
Alexis
New Member
2 Posts |
Posted - Jan 06 2018 : 3:35:14 PM
|
I just bought a licence again and downloaded the last build, and all works perfect.
I do not complain about having bought this license since I am happy with the product. however, I think there should be a fix for those who have an earlier version, since it makes the product unusable. |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jan 06 2018 : 4:14:09 PM
|
Build 2248 is not necessary for the Windows 10 updates to work and prevent the problems related to the Windows 10 bugs that have been causing problems since last summer.
Build 2248 fixes the crash in Code Inspection that started occurring with the 15.5 update of VS2017. To deal with that crash, you had three options: 1) disable Code Inspection 2) don't use the 15.5 update 3) use VA build 2248
|
|
|
Topic |
|