| Author |
 Topic  |
|
|
TheDrej
New Member
4 Posts |
 Posted - Dec 05 2024 : 6:44:30 PM
|
Hello,
I've just recently had VAssist mostly stop working in my C++ (Unreal Engine) project, but it works fine in my C# project.
Visual Studio 2022 v17.11.1
Visual Assist X build 2024.8
Things failing in C++ project (that I know of):
- No navigation bar (i.e. list methods in current file with alt-m)
- Cannot go to symbol definition
- Cannot find references
- No syntax colouring
- No quick refactoring icon or menu (alt-shift-q)
What works in C++ project:
- Find files (alt-shift-o)
- Find symbol (alt-shift-s)
I recently installed the AWS Toolkit extension and I discovered that if I disable that extension everything works! I searched these forums and found that this is a known issue for at least a year (Dec 18, 2023) and has a case number.
Case# 164067
Could you please provide the VAssistX community an update on when this is going to be fixed. The AWS Toolkit is not an obscure extension and encountering this conflict is extremely frustrating and difficult to figure out (I did a whole bunch of deleting, resetting & re-installing before figuring this out).
Thanks,
Reference posts with the same issue:
- https://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=20598
- https://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=20615
|
Edited by - TheDrej on Dec 05 2024 6:46:08 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19110 Posts |
Posted - Dec 06 2024 : 09:51:10 AM
|
Apologies for this, this is still in our list of bugs to fix. It is down as a high priority bug, but unfortunately I don't currently have an estimate for when this will be fixed.
Still, having someone else run into this will hopefully help get this looked at soon, since it is something that, as you may have noticed, very rarely comes up.
case=164067 |
zen is the art of being at one with the two'ness |
 |
|
|
TheDrej
New Member
4 Posts |
Posted - Dec 06 2024 : 1:01:42 PM
|
Hi,
quote:
Originally posted by feline
Still, having someone else run into this will hopefully help get this looked at soon, since it is something that, as you may have noticed, very rarely comes up.
case=164067
The thing is, it may seem like it rarely comes up, but that may not really be true. Imagine users have the AWS Toolkit extension installed for a while then one day they decide to try VAssistX and install the trial version and it just doesn't work. They're not going to create an account and make a support request, but ultimately believe that VAssistX is a bad product and move onto something else.
Or like in my case, it's working fine in a C# project and then you switch to a C++ project and VAssistX is just broken. Figuring out that it's because of some conflict with AWS Toolkit is extremely difficult and they'll probably give up and you'll never know.
I don't believe your support cases on this specific issue accurately reflect how often this issue is encountered. Never understimate the lack of desire to create a support forum account and make a post (I almost didn't) ;)
All to say this should really be a higher priority fix as it's been around at least a year and makes VAssistX completely unusable.
Cheers
|
Edited by - TheDrej on Dec 06 2024 1:03:16 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19110 Posts |
Posted - Dec 10 2024 : 11:28:50 AM
|
I do actually completely agree with you. It's one of my background concerns, that we don't have an accurate sense of which problems are causing the most problems for our users. Unfortunately that's not an easy problem to solve, without having VA report back on anything odd that happens. But this is something we avoid unless you manually send us logs, since a lot of our users work in situations where the details of what they are doing, and working on, are confidential.
Working off of what is reported is very imperfect and quite biased system. But it does avoid the real concerns of collecting a load of data automatically in the background. |
zen is the art of being at one with the two'ness |
|
|
|
TheDrej
New Member
4 Posts |
Posted - Dec 11 2024 : 11:31:31 AM
|
Has anyone on the support end tried installing Visual Studio + AWS Toolkit extension + VAssistX extension to reproduce it? This might be 100% reproducible.
If it doesn't repro, I can enable logging on my end and send the logs over. If so let me konw the procedure for sending logs to your team.
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19110 Posts |
Posted - Dec 11 2024 : 12:13:01 PM
|
I have reproduced / confirmed this problem. Once someone else reported they had seen an issue after installing the AWS Toolkit extension I installed it myself. As you are aware, the problem is very obvious and easy to spot, once you know the trigger. If only all bugs were so easy to confirm and reproduce.
This is down as a high priority and important bug, unfortunately it's one of several such bugs we are currently addressing.
As you probably know from your own experience, prioritising between multiple bug reports and feature requests isn't always easy, but we do our best. One consideration is how many people a problem or feature seems to impact. To be honest this is educated guesswork, but we do listen to what people are saying, and asking for, and this helps us to prioritise. |
zen is the art of being at one with the two'ness |
|
|
|
TheDrej
New Member
4 Posts |
Posted - Dec 13 2024 : 1:23:27 PM
|
You're welcome and I hope it is an easy enough fix :) It's a bug that unfortunately affects both new and existing users.
So how would customers get informed once the fix is released? I don't think we can subscribe to the case #. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19110 Posts |
Posted - Dec 16 2024 : 07:22:28 AM
|
At the top of the page, in the right hand corner, you should see a link "Subscribe to topic", which will let you get notifications of replies to this topic. The topic will be updated when we release a fix. We go through and mark which cases have been fixed in each new build.
You can also keep an eye on the release notes, so you will know what has changed in a new build:
https://www.wholetomato.com/features/whats-new |
zen is the art of being at one with the two'ness |
|
|
|
herve
New Member
France
2 Posts |
Posted - Feb 12 2025 : 08:39:10 AM
|
Hello
I also have the same problem.
I am one of the people evaluating AWS Q for my company. In my team we mainly develop in C++ using Visual Studio 2022 pro and Visual Assist has been a valuable help, but if the company decides to use AWS Q, we will be forced to abandon VA if it cannot work with AWS Q. How can I get VA to work with AWS Q?
I hope to have a solution soon. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19110 Posts |
Posted - Feb 12 2025 : 12:17:49 PM
|
| Unfortunately I don't have a work around or a solution yet, but this is down as a very urgent bug, which we are hoping to get addressed very soon. I have added a note about the problems it is causing you, which will hopefully add weight to things. |
zen is the art of being at one with the two'ness |
|
|
|
herve
New Member
France
2 Posts |
|
|
feline
Whole Tomato Software
United Kingdom
19110 Posts |
Posted - Feb 18 2025 : 07:56:35 AM
|
Wonderful news, thank you for the update.
I have just double checked this here, and the fix is working for me as well, so if anyone still has problems please do let us know so we can try to work out what is going wrong for you. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Visual Assist X fails with AWS Toolkit extension
