Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 GO button gets randomly huge on Visual Studio 2022

You must be registered to post a reply.
Click here to register.

Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji

Forum code is on.
Html is off.

Check to subscribe to this topic.

T O P I C    R E V I E W
kuzniar Posted - Jan 12 2023 : 11:24:10 AM
I am using current version of Visual Assist and newest version of Visual Studio 2022 (Microsoft Visual Studio Professional 2022 (64-bit) -Current. Version 17.4.3). Randomly, but at least once a day I have a bug, that GO button (top left corner) gets big. The only way to make it small again is to close Visual Studio completely.

30   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Apr 26 2023 : 10:13:04 AM
The problem does seem to be random. I have emailed you about this.
kuzniar Posted - Apr 26 2023 : 09:49:29 AM
Love this message. I didn't experience this problem for a long period of time, until today when it happened already twice.
It happened when I was switching between the files using your feature "Open File in Solution" Shift + Alt + O.
It happens randomly though.
feline Posted - Apr 25 2023 : 09:36:16 AM
We are finding this very difficult to reproduce on demand, but we do think we have a fix for this internally. ClementC and tbrammer I have emailed you about this.
tbrammer Posted - Apr 25 2023 : 06:45:17 AM
I have the same problem.
I can solve it either by disabling the VA Navigation bar or by restarting VS 2022. Both options are nonsatisfying.
I'm using two monitors. The one with VS running is in portait mode, the other one landscape.
They are connected to a docking station. I switch between working from home and in the office.
My monitors in the office have different types and resolutions then the ones at home.
I take my laptop and the docking station with me.

VAX System info: (some private data xxx-ed)
License: Standard xxxxx Support ends 2026.xx.xx
VA_X64.dll file version 10.9.2476.0 built 2023.01.19
DevEnv.exe version 17.5.33516.290 Enterprise
msenv.dll version 17.0.33516.290
Comctl32.dll version 6.10.19041.1110
Windows 10 10.0 21H2 Build 19044.2846
20 processors (x86-64)
Language info: 1252, 0x407

Platform: Project defined
Stable Includes:
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\include;
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Include\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\cppwinrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\um;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary\VS\UnitTest\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary\VS\include;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.35.32215\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.35.32215\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\include;
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include;

Other Includes:

Stable Source Directories:
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\atlmfc\src\mfc;
C:\Program Files (x86)\Windows Kits\10\Source\10.0.22621.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Auxiliary\VS\src;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.35.32215\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.35.32215\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.35.32215\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.35.32215\atlmfc\src\mfc;
C:\Program Files (x86)\Windows Kits\10\Source\10.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\crt\src;
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\atlmfc\src\mfc;

ClementC Posted - Apr 19 2023 : 08:09:27 AM
Yes, thank you, I will disable it for now, I didn't even think of that (sometimes you just get annoyed at things and don't realise you could easily turn it off).
I use Alt-M quite a lot to jump to functions but I can definitely live without it until the next release : )

Thanks a lot!
feline Posted - Apr 19 2023 : 07:12:04 AM
Thank you for the settings. Unfortunately no sign of the problem yet, but there is good news. We believe we have found and fixed the problem internally, and the fix will be in the next release.

Since we are finding this very difficult to reproduce on demand we are not totally sure of the fix, but are hopeful.

For now, is turning off the VA navigation bar, via:

VA Options -> Display -> Display VA Navigation Bar:

a solution? Since you are seeing this so often, rather than occasionally, it might be worth it. This will stop the Alt-M list working, but you can still use VA Outline to get a sense of the current file, and to jump to functions in the file.
ClementC Posted - Apr 19 2023 : 06:34:58 AM
Thank you for the swift reply! I've emailed the settings as you requested, I hope it helps!
feline Posted - Apr 19 2023 : 06:23:48 AM
Thank you for the details. Would it be possible to get a copy of your settings? I can at least try them and see if I can reproduce the narrow band of not drawn screen bug, which may or may not be related to this. At least I did manage to reproduce that bug on demand. To export your settings you can use:

VA Options -> Performance -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings

Please send me the files via email:

[email protected]

including this thread ID or URL in the description, so we can match it up.
ClementC Posted - Apr 18 2023 : 1:00:40 PM
Hi, I'm getting the exact same issue, that's what I'm using:
VS Community 2022, VA 2022.3
VA_X64.dll file version 10.9.2458.0 built 2022.07.29
DevEnv.exe version 17.4.33103.184 Community
msenv.dll version 17.0.33103.184
Comctl32.dll version 6.10.22621.436
Windows 11 11.0 22H2 Build 22623
8 processors (x86-64)
Language info: 1252, 0x809

I only have Visual Assist and P4VS installed as extensions.
I'm using two monitors but they are exactly the same model, same resolution, same DPI. It seems to happen when I tab out to another software and back in. I've seen it happen only with .cs files but when I use cpp I don't tab out as much so it may be why?

It happened around 10 times today and can't find any way to solve it other than restarted VS which is not great : (
feline Posted - Apr 11 2023 : 10:55:40 AM
Which file extensions are you getting this problem with?

Are you aware of any form of pattern to this bug? Anything that might be a possible trigger? Clearly there is a problem here, but I am not really making any progress reproducing this here so far, which is clearly unhelpful.
equalent Posted - Apr 10 2023 : 05:02:46 AM
This exact thing happened to me as well, twice already. VS 2022 17.5.3, VA 2476, a single 2560x1440 monitor with 100% scale
feline Posted - Mar 28 2023 : 11:38:15 AM
Finally got it happening on demand. At first it happened, but then when I tried to reproduce it I could not get it to happen reliably. For me it is related to first closing and then opening code files. Just opening files without closing them isn't enough to trigger it. Also it depends on the IDE Environment font and color settings, probably the size of IDE elements.


Hopefully this will offer a clue as to the really tall navigation bar problem as well.
feline Posted - Mar 21 2023 : 1:05:40 PM
Urg! I have looked up some settings you sent me, Feburary 2023, and imported them into Windows 10, VS2022 with VA 2476.0

I then set up a test for this with multiple different file extensions, but no sign of what you are seeing. But when opening a .cs or .cpp file I get this:

I assume this is what you are describing. Now to figure out the trigger, if possible.

Which still leaves the question of why I am seeing this under different conditions to you.
Uniwares Posted - Mar 21 2023 : 11:34:19 AM
A few more insights: when VS loads an solution, it also loads the previously opened documents, but it does not instantiate them until they become visible the first time. What I noticed is that when I activate such a tab for the first time, there is this slight calculation error which leaves 2 pixels space under the VA navbar that doesn't get repainted ever. When I open a document from the solution or somewhere else, the VA navbar is automatically those 2 pixels larger and no unpaintable area is left. This is not exactly the effect of the large button, but points to a general sizing problem when instantiating the navbar. Probably some post-initialize resize of the editor area that passes unnoticed from VA. My guess is that it has to do with font sizing/scaling, thus it probably doesn't happen on "standard" display settings. Just guessing.
Uniwares Posted - Mar 09 2023 : 11:30:49 AM
Noticed that sometimes the button doesnt get notably bigger, but the whole navigation bar gets a few pixels larger, and the area that is outside the VA controls becomes a no-redraw area.
feline Posted - Mar 09 2023 : 10:27:43 AM
Which file extension or extensions do you see this in?

Any hints of a pattern or a trigger for this?
androidqueen Posted - Mar 08 2023 : 12:48:46 PM
Just adding that I am also periodically getting this issue.

Visual Studio 2022
VA_X64.dll file version 10.9.2471.0 built 2022.11.25
Single ultrawide monitor
feline Posted - Feb 21 2023 : 1:05:15 PM
Are you seeing this with the same file extensions as above, or are you seeing this with different file extensions?

Is there any form of pattern that you have noticed to this problem? It is very rare, but with several different people seeing it I am wondering if there is a common trigger.
khashfirestorm Posted - Feb 21 2023 : 09:55:44 AM
I have the same issue. Developing in Unity + VS + VA,
Microsoft Visual Studio Community 2022 (64-bit) - Current, Version 17.4.4
visual assist 10.9.2476.0 built 2023.01.19
feline Posted - Feb 02 2023 : 05:55:39 AM
Totally normal files there, so no obvious clues. I was thinking of a bug report about problems with the VA navigation bar that used, from memory, XAML or HTML files where the IDE reported an error in the file structure, and interacting with the error message could trigger the problem. So much for that theory.
kuzniar Posted - Feb 02 2023 : 03:33:18 AM
.cpp, .hpp, .h, CMakeLists.txt
feline Posted - Feb 01 2023 : 06:20:56 AM
What file extension, sort of code file, were you working in when this happened? I am just wondering if you were working in a "normal" code file or something a little bit different, in case this offers a clue.

Either way, certainly not a one off problem.
kuzniar Posted - Jan 31 2023 : 10:19:31 AM
It happened to me right now. 2 monitors + 3rd as laptop. During the build I was browsing web and using Alt + Tab to see what is going on with the build. And suddenly I can see that It got huge again.
For the last few days, the problem did not appear.
(No profiler installed yet)
feline Posted - Jan 23 2023 : 08:14:39 AM
A second report of the same problem, but so far no good idea of why it happens there either:

feline Posted - Jan 17 2023 : 07:18:39 AM
This is a little complex, but hopefully these instructions will be clear an easy to follow. Can you first download the VS2022 specific installer for Visual Assist from:


Next you will need extra details about the IDE install to create a test profile, which you get from running:

"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe"

There will be a set of lines for each different version of Visual Studio that you have installed. For the version you want to install into, you want the "productPath", "dispalyName" and "installationVersion" lines, e.g.

productPath: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
displayName: Visual Studio Professional 2022
installationVersion: 17.3.32901.215

You can then use the information from these three lines to make sure that the following command has the correct command line parameters. The values are:

/appidname: = displayName:
/appidinstallpath: = productPath:
/skuVersion = installationVersion:

The "/skuName:" value is one of "Community / Pro / Enterprise", note for the Professional version it is "Pro", not the expected "Professional".

The working command, for VS2022, using the values above, is - split into lines to make it easier to read and edit:

"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\VSIXInstaller.exe"
/appidinstallpath:"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe"
/appidname:"Visual Studio Professional 2022"
/rootSuffix:"VATest" "C:\Users\%USERNAME%\Downloads\VA_X_Setup2471_0_x64.vsix"

The "rootSuffix" is the name of the test profile you want to install to, and this will be created if it does not already exist. The final parameter is the path of the VSIX installer for Visual Assist that you want to install. Once you have the command set up, the only parts you should need to edit are the skuVersion and the path to the VSIX file, can you please close all instances of Visual Studio and run this command.

Running this command installs VA into the test profile, but it does not load the test profile. If you created the test profile by installing VA, when you run the test profile it will be using the default IDE settings, without asking you which settings you want to use.

To now load the test profile you use the command:

"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest

To load your normal, default profile just load the IDE normally. To return to this test profile again, pass the /RootSuffix command line switch when loading the IDE. You can run both profiles at the same time, next to each other. In VS2019 and VS2022 the profile name will be shown just under the close button, in the top right hand corner of the main IDE window. If you export your IDE settings from your main profile you can them import them into the test profile.

You should only have the default extensions plus Visual Assist installed into the test profile, so can you please try working in the test profile for a day or two, and see if you get this problem?
kuzniar Posted - Jan 17 2023 : 05:00:14 AM
Yes, sure, do I need to enable something or just disable or other extensions?
feline Posted - Jan 12 2023 : 12:34:10 PM
Thank you for explaining. So it could be multiple monitor related, or that might be a red herring.

I recognise most of these extensions, and would not expect any problems from any of them.

Would you be able to try running a test profile for a couple of days? The idea is a separate profile in Visual Studio with only Visual Assist installed as an extension, to see if this stops the problem from happening. By testing this in a separate profile we don't disturb your default profile and installed extensions.
kuzniar Posted - Jan 12 2023 : 12:04:15 PM
At home I connect my laptop to a single 4k monior using HDMI cable and I work on dual monitor setup (so my laptop + single external display).
I don't use any utilities to handle multiple monitors - just Windows (Windows 10 Enterprise, version - 21H2)
I am using C++
I have installed such extensions:
Clang Power Tools, Live Share 2022, Visual Studio Spell Checker (VS2022 and later), VSColorOutput64, Visual Assist, Test Adapter for Google Test, Close Tabs, File Icons

feline Posted - Jan 12 2023 : 11:56:04 AM
When you are at home, are you connecting the laptop to the display, or is it just a system with a single display? It sounds like a system with just a single display, but I just wanted to be sure. This reminds me of some problems we had with monitors with different DPI settings, but these problems are all supposed to be fixed now.

Are you using any utilities to handle multiple monitors? For example I use Display Fusion, which has the feature to move a window to a different monitor via a keyboard shortcut. I am wondering if something else interacting with the IDE could be a factor.

Which programming language or languages are you using in your solution?

Do you have any other extensions installed?
kuzniar Posted - Jan 12 2023 : 11:35:54 AM
Which version of VA are you using? - VA_X64.dll file version 10.9.2471.0 built 2022.11.25
Do you have more than one monitor on your system? - Yes 3 displays (1 from laptop <1920x1200 150% scale> and 2 external monitors <1920x1080 100% scale>)
Do you have a high refresh rate monitor? - 60 Hz each

At home I also connect to a single 4k display and the error occurs as well.
I can't tell when exactly this problem happens, I can't reproduce this problem as well. During the workday, on average this issue happens at least once.

If it happen again I will try to close all open files as you suggested

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000