appidname:"Visual Studio Professional 2022" appidinstallpath:"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe" "C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\VSIXInstaller.exe" The working command, for VS2022, using the values above, is - split into lines to make it easier to read and edit: ![]() The "/skuName:" value is one of "Community / Pro / Enterprise", note for the Professional version it is "Pro", not the expected "Professional". You can then use the information from these three lines to make sure that the following command has the correct command line parameters. ProductPath: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exeĭisplayName: Visual Studio Professional 2022 For the version you want to install into, you want the "productPath", "dispalyName" and "installationVersion" lines, e.g. There will be a set of lines for each different version of Visual Studio that you have installed. "%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe" Next you will need extra details about the IDE install to create a test profile, which you get from running: Can you first download the VS2022 specific installer for Visual Assist from: ![]() This is a little complex, but hopefully these instructions will be clear an easy to follow. Yes, sure, do I need to enable something or just disable or other extensions? By testing this in a separate profile we don't disturb your default profile and installed extensions. 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. I recognise most of these extensions, and would not expect any problems from any of them. So it could be multiple monitor related, or that might be a red herring. I don't use any utilities to handle multiple monitors - just Windows (Windows 10 Enterprise, version - 21H2)Ĭlang Power Tools, Live Share 2022, Visual Studio Spell Checker (VS2022 and later), VSColorOutput64, Visual Assist, Test Adapter for Google Test, Close Tabs, File Icons Which programming language or languages are you using in your solution?ĭo you have any other extensions installed?Īt 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 am wondering if something else interacting with the IDE could be a factor. This reminds me of some problems we had with monitors with different DPI settings, but these problems are all supposed to be fixed now.Īre 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. 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. If it happen again I will try to close all open files as you suggested During the workday, on average this issue happens at least once. I can't tell when exactly this problem happens, I can't reproduce this problem as well. 0 built 2022.11.25ĭo you have more than one monitor on your system? - Yes 3 displays (1 from laptop and 2 external monitors )ĭo you have a high refresh rate monitor? - 60 Hz eachĪt home I also connect to a single 4k display and the error occurs as well. ![]() Which version of VA are you using? - VA_X64.dll file version. Zen is the art of being at one with the two'ness If you close all open files, and then just open a single code file does this make any difference, or have you already tried this? ![]() My first theory is that there is something about your display configuration that is a factor.Īre you aware of any form or pattern to what triggers this problem? It happens randomly when I am switching between tabs or moving tabs around the screen.ĭo you have more than one monitor on your system? If so, do they have different DPI settings? I can't figure out what makes the go button so huge. The effect with duplicated GO symbol is triggered by resizing the width of the window. The only way to make it small again is to close Visual Studio completely. Randomly, but at least once a day I have a bug, that GO button (top left corner) gets big. I am using current version of Visual Assist and newest version of Visual Studio 2022 (Microsoft Visual Studio Professional 2022 (64-bit) -Current. GO button gets randomly huge on Visual Studio 2022 Whole Tomato Software Forums - GO button gets randomly huge on Visual Studio 2022
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |