| T O P I C R E V I E W |
| AlbanCarpool |
Posted - Jan 11 2024 : 10:46:17 AM
Hello, we are having an issue with Visual Assist in our company (Carpool Studio). In 2 days, three of us have our Visual Assist that doesn't work anymore with no error message and no licence issue message.
The thing that we suspect is that the three of us did a reboot requested by our company AntiVirus (ESET) for an update.
Here is the state of our Visual Assist (only open file works)
|
| 10 L A T E S T R E P L I E S (Newest First) |
| AlbanCarpool |
Posted - Jan 15 2024 : 08:00:06 AM
Thank you! |
| feline |
Posted - Jan 15 2024 : 06:54:36 AM
Excellent, thank you for the update, I am glad we have finally found the trigger. Hopefully our developers will have a fix for this fairly soon. |
| AlbanCarpool |
Posted - Jan 15 2024 : 04:07:57 AM
I confirm that disabling AWS Toolkit fixed our Visual Assist for all of us.
If you have updates on AWS Toolkit working with Visual Assist, I'm interested.
Thanks again |
| AlbanCarpool |
Posted - Jan 15 2024 : 03:01:27 AM
Will Whole Tomato investigate with AWS the source of the issue to try to find a fix to be able to use AWS Toolkit with Visual Assist together? |
| AlbanCarpool |
Posted - Jan 15 2024 : 02:59:54 AM
Good morning, good news! Visual Assist works again for me disabling extension AWS Tooktip. I'm waiting for the other employees to arrive at office to test on their computer. I keep you in touch.
Thanks a lot for your support and to have resolved my issue!
. |
| feline |
Posted - Jan 12 2024 : 12:55:04 PM
Can you please check and see if you have the extension "AWS Tooktip for Visual Studio 2022" installed, and if so, try disabling this extension in the dialog:
IDE Extensions menu -> Manage Extensions
For me, this extension is causing this problem on two different test systems, so it could well be the trigger for you as well.
case=164067 |
| feline |
Posted - Jan 11 2024 : 12:44:08 PM
Many thanks for trying that. Anti-virus would have been a nice and "easy" answer, but apparently it isn't the problem.
You are seeing exactly the same pattern with VA working in C# but failing in C++ as another customer, but so far I don't know what the trigger could be. Do you have any other extensions installed?
Do you have any employees who are not seeing the problem?
With all instances of Visual Studio closed, can you please run regedit and set:
HKEY_CURRENT_USER\SOFTWARE\Whole Tomato\Logging = 1
this will cause VA to start logging from as soon as it has started loading.
Can you please then load a C++ solution, and once the IDE has finished loading, and the problem is clear, close the IDE and send me the VA log files. If we are lucky they will offer some clues.
The generated log files should be:
%TEMP%\va.log
%TEMP%\vassist.log
C:\Users\%USERNAME%\AppData\Local\Microsoft\VisualStudio\17.xxxx\Extensions\<random hash>\Data\Startup.log
C:\Users\%USERNAME%\AppData\Local\Microsoft\VisualStudio\17.xxxx\Extensions\<random hash>\Data\17_1\errors.log
Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up. |
| AlbanCarpool |
Posted - Jan 11 2024 : 11:52:45 AM
We uninstalled the Antivirus ESET + reboot. Sadly it didn't fix the issue. VA doesn't work on C++ projects (but it works on C# project) |
| AlbanCarpool |
Posted - Jan 11 2024 : 11:41:55 AM
I just tried to create a C# project and Visual Assist seems to work fine in this project.
I tried to load other C++ project, VA doesn't work neither in these projects.
I'm checking with our IT how to remove/disable our anti virus to test |
| feline |
Posted - Jan 11 2024 : 11:16:54 AM
Apologies for this problem. Are you seeing this in a C# or a C++ solution?
If this is happening in C++, can you please try creating a new, default C# solution, and see if VA works there? I am asking since we have another user who is seeing a similar problem, and for them VA works in a C# solution but isn't active in a C++ solution, so I am wondering if you are seeing the same pattern.
Are you able to disable your AntiVirus temporarily, or add an exclusion for Visual Studio and Visual Assist, to see if it is a factor? If you are seeing the same problem, I am still trying to find a trigger here, so its possible AntiVirus is a factor. |
