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
 Suggestions list appears top left
 New Topic  Reply to Topic
 Printer Friendly
Previous Page
Author Previous Topic Topic Next Topic
Page: of 2

sosedada
Senior Member

USA
30 Posts

Posted - Nov 16 2021 :  09:37:45 AM  Show Profile  Reply with Quote
I've seen it on a 186 project c++, c++/cli, and c# solution, another 266 projects solution but with different proportions (mostly c#). Rebuilding symbol database did not help (nor clearing cache).

A fresh checkout of the first solution did not show the error and is successfully inspecting.
Go to Top of Page

sosedada
Senior Member

USA
30 Posts

Posted - Nov 16 2021 :  09:59:32 AM  Show Profile  Reply with Quote
Deleting the .vs directory seems to resolve the popup dialog location and the error at startup. Inspections are also functional (except some parsing failures, but that's another story)
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 16 2021 :  11:17:04 AM  Show Profile  Reply with Quote
Thank you for the update. This seems to confirm that a problem with the IDE intellisense symbol database (or related files) is the cause of the problems you are seeing.

It is possible the problem will stay fixed, or it might come back with time.

I am more than happy to look at the parsing problems with you, but probably best in a new thread, for ease

Can anyone else who is seeing the code inspection error on startup also try deleting (renaming to be extra safe) the .vs folder and see if this fixes the problem for you as well?

zen is the art of being at one with the two'ness
Go to Top of Page

sosedada
Senior Member

USA
30 Posts

Posted - Nov 16 2021 :  8:43:35 PM  Show Profile  Reply with Quote
I installed the new release of VS and after restart one of my solutions showed the error and the other didn't. So, deleting the .vs doesn't seem to be a permanent fix.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 17 2021 :  07:11:43 AM  Show Profile  Reply with Quote
Somehow I am not surprised, this seemed almost to easy.

On the solution that is still showing the error, is this every time, or does it seem random?

Is this VS2019 or VS2022? I am wondering about testing with a second profile, but that currently requires VS2019, so the IDE version matters.

zen is the art of being at one with the two'ness
Go to Top of Page

sosedada
Senior Member

USA
30 Posts

Posted - Nov 17 2021 :  11:29:47 AM  Show Profile  Reply with Quote
Solution U re-manifested the bug after upgrading to VS 2022 17.0.1. Solution E has survived a few restarts and still has inspections.

Attempting to option Solution U in VS 2019 now crashes, which is neat. Good thing I like 2022 so much more. Getting tired of deleting .vs folders :)

Restarting Solution U in 2022 is now properly showing the code completion prompt. *shrug*
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 17 2021 :  12:25:09 PM  Show Profile  Reply with Quote
Are you still working in VS2019? A crashing IDE is very serious, obviously, and needs to be looked at!

Are you able to get a mini dump from the VS2019 crash? If you are not sure how to do this, this page explains how:

https://support.wholetomato.com/default.asp?W303

In VS2022, do you mean that code inspection is working correctly, scanning your code and reporting suggestions? Or do you mean that you are back go getting the error message about it not working on solution load?

zen is the art of being at one with the two'ness
Go to Top of Page

sosedada
Senior Member

USA
30 Posts

Posted - Nov 17 2021 :  12:47:33 PM  Show Profile  Reply with Quote
At this moment in time, everything is working correctly. I'll try to get a minidump later. Gotta crank out some code :)
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 18 2021 :  05:36:23 AM  Show Profile  Reply with Quote
Working better is excellent news, long may it continue!

Obviously if, although we hope not, this ever comes back again I am here to offer as much help and support as I am able to.

zen is the art of being at one with the two'ness
Go to Top of Page

ViniestJester
New Member

3 Posts

Posted - Nov 20 2021 :  06:13:30 AM  Show Profile  Reply with Quote
I'm using VS2022 with the current trial version of VAX. As for the frequency it happens almost every time. Rebuilding the symbol database only fixes it for that particular session, only worked a couple of times without having to rebuild the database.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 22 2021 :  08:13:55 AM  Show Profile  Reply with Quote
The fact that this is very nearly every time is interesting, and hopefully helpful for testing this problem.

Can you please try making a new, default solution, to see if this is somehow a solution specific problem?

Do you have VS2019 installed as well? Or even an earlier version of the IDE? I am just wondering if this is IDE version specific as well, or not.

zen is the art of being at one with the two'ness
Go to Top of Page

ViniestJester
New Member

3 Posts

Posted - Nov 22 2021 :  4:53:09 PM  Show Profile  Reply with Quote
I have VS2017 installed. I created 2 default Windows Desktop projects, one in VS2017 and other in VS2022 with the same trial version of VAX.
I don't see the issue happen in VS2017 after opening the project multiple times after the first creation, but it did occur in the VS2022.
The first creation of the project doesn't seem to cause the issue in either of the versions.
Go to Top of Page

ChrisG
Whole Tomato Software

USA
252 Posts

Posted - Nov 22 2021 :  4:56:19 PM  Show Profile  Reply with Quote
This is fixed in build 2021.5, which was released today.

https://support.wholetomato.com/default.asp?W404#2440
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 23 2021 :  12:01:01 PM  Show Profile  Reply with Quote
Does installing the latest version of VA, 2021.5, make any difference?

Do you have any other extensions installed?

zen is the art of being at one with the two'ness
Go to Top of Page

jorenjoestar
New Member

Italy
6 Posts

Posted - Nov 23 2021 :  4:11:39 PM  Show Profile  Reply with Quote
Hello there, the new version of VAX (2440_0) fixes all my problem on Visual Studio 2022.
So a big THANK YOU! :)
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
17503 Posts

Posted - Nov 24 2021 :  06:16:46 AM  Show Profile  Reply with Quote
Thank you for the update, excellent news, really glad this has helped so much!

zen is the art of being at one with the two'ness
Go to Top of Page

ViniestJester
New Member

3 Posts

Posted - Nov 24 2021 :  07:02:45 AM  Show Profile  Reply with Quote
Yeah the issue doesn't occur after updating to VAX 2021.5. Thanks to everyone!
Go to Top of Page
Page: of 2 Previous Topic Topic Next Topic  
Previous Page
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2021 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000