| Author |
 Topic  |
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
 Posted - Nov 14 2024 : 3:14:52 PM
|
I've reported this issue to Microsoft, and they've helped me track it down to the Visual Assist X extension:
https://developercommunity.visualstudio.com/t/VS2022-keeps-losing-the-GitHub-Copilot/10786000?viewtype=all
I have an instance of Visual Studio 2022 (version 17.12.0) that is losing the upper-right GitHub Copilot, feedback icons. The same also occurred in 17.11.x using VAX 2520, and 2537.
If I uninstall or disable Visual Assist they come back. Or if I run the Visual Studio installer Repair, which uninstalls Visual Assist, then it also comes back.
I attached my .reg settings on the link above if you want to try to reproduce it. This is the only machine I have Visual Studio 2022 installed on, so it's the only one I have to test.
Thank you!
--
Rick C. Hodgin
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 15 2024 : 07:01:30 AM
|
When this happens, if you hover the mouse over where the buttons should be do you get a mouse tooltip?
We have had some problems with missing icons before, but they were on the toolbar, and have long since been fixed. So I am wondering if we are missing the graphic for the buttons, or if the entire button is gone.
Are you aware of a trigger for the problem? You say a repair fixes this, but does it only stay fixed while VA is disabled? Or does it break again as soon as VA is enabled? |
zen is the art of being at one with the two'ness |
 |
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 15 2024 : 12:27:51 PM
|
If I mouse over where they should be nothing happens.
As far as I can tell, the only thing that triggers it is Visual Assist being installed / uninstalled. And, it's been probably from 17.8 and later.
--
Rick C. Hodgin |
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 15 2024 : 1:28:55 PM
|
I am not seeing it here, and no one else seems to be reporting this so far. So, lets see if this is profile specific on your machine. Some odd problems are, so this could be.
To test this, can you first download the VS2022 specific installer for Visual Assist from:
https://downloadfiles.idera.com/WholeTomato/VA_X_Setup2537_0_x64.vsix
Next you will need extra details about the IDE install to create a test profile. To get these details, please open a Windows command prompt window, and inside the window run the command:
"%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.9.34607.119
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"
/skuName:Pro
/appidname:"Visual Studio Professional 2022"
/skuVersion:17.9.34607.119
/rootSuffix:"VATest" "C:\Users\%USERNAME%\Downloads\VA_X_Setup2537_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.
Do you see the same problem in the test profile, or do the buttons show up correctly there? |
zen is the art of being at one with the two'ness |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 15 2024 : 4:59:38 PM
|
productPath: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
displayName: Visual Studio Professional 2022
installationVersion: 17.12.35506.116
The command I used to run (d:\downloads\vax\):
"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" /skuName:Pro /appidname:"Visual Studio Professional 2022" /skuVersion:17.12.35506.116 /rootSuffix:"VATest" "d:\downloads\vax\VA_X_Setup2537_0_x64.vsix"
It came up: VSIX Installer
Install -- Visual Assist -- Digital Signature: None
Clicked [Modify]. "Your modifications have been successfully applied..."
To launch:
"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest
By default, comes up in dark mode. The icons are missing:
I told it to uninstall Visual Assist upon exit. Exited. It uninstalled. Re-ran the launch command again:
"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest
It then shows the icons returned, along with the [VATEST] label, which I've never seen before (that label / text in that area):
--
Rick C. Hodgin
|
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 15 2024 : 5:04:07 PM
|
Here's the full result:
-----[ Begin ]-----
C:\Users\rhodgin>"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe"
Visual Studio Locator version 3.1.7+f39851e70f [query version 3.12.29.16771]
Copyright (C) Microsoft Corporation. All rights reserved.
instanceId: 330fe509
installDate: 5/4/2023 5:08:43 PM
installationName: VisualStudio/17.12.0+35506.116
installationPath: C:\Program Files\Microsoft Visual Studio\2022\Professional
installationVersion: 17.12.35506.116
productId: Microsoft.VisualStudio.Product.Professional
productPath: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
state: 4294967295
isComplete: 1
isLaunchable: 1
isPrerelease: 0
isRebootRequired: 0
displayName: Visual Studio Professional 2022
description: Professional IDE best suited to small teams
channelId: VisualStudio.17.Release
channelUri: https://aka.ms/vs/17/release/channel
enginePath: C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service
installedChannelId: VisualStudio.17.Release
installedChannelUri: https://aka.ms/vs/17/release/channel
releaseNotes: https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-v17.12#17.12.0
resolvedInstallationPath: C:\Program Files\Microsoft Visual Studio\2022\Professional
thirdPartyNotices: https://go.microsoft.com/fwlink/?LinkId=661288
updateDate: 2024-11-13T03:54:33.7655732Z
catalog_buildBranch: d17.12
catalog_buildVersion: 17.12.35506.116
catalog_id: VisualStudio/17.12.0+35506.116
catalog_localBuild: build-lab
catalog_manifestName: VisualStudio
catalog_manifestType: installer
catalog_productDisplayVersion: 17.12.0
catalog_productLine: Dev17
catalog_productLineVersion: 2022
catalog_productMilestone: RTW
catalog_productMilestoneIsPreRelease: False
catalog_productName: Visual Studio
catalog_productPatchVersion: 0
catalog_productPreReleaseMilestoneSuffix: 6.0
catalog_productSemanticVersion: 17.12.0+35506.116
catalog_requiredEngineVersion: 3.12.2149.20818
properties_campaignId: 1707
properties_channelManifestId: VisualStudio.17.Release/17.12.0+35506.116
properties_nickname:
properties_setupEngineFilePath: C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe
C:\Users\rhodgin>
-----[ End ]-----
--
Rick C. Hodgin |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 18 2024 : 09:23:10 AM
|
I've tried going back to 2520, and 2511. Both of them exhibit the same behavior: When VA is installed, no icons. When it's uninstalled, icons.
The only possible unusual thing I'm doing is I also have Visual Studio 2008 Professional installed, and I have not been applying any of these update changes to that installation. I went with this one, and have been keeping it:
License: Standard (... / ...) Support ends 2025.03.27
VA_X.dll file version 10.9.2522.0 built 2024.05.31
DevEnv.exe version 9.0.21022.8 Professional
msenv.dll version 9.0.21022.8
Font: Fantasque Sans Mono 13 (pixels)
Comctl32.dll version 6.10.19041.4355
Windows 8 6.2 Build 9200
8 processors (x86-64, WOW64)
Language info: 1252, 0x409
Platform: Win32
Stable Includes:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include;
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\atlmfc\include;
C:\Program Files\Microsoft SDKs\Windows\v6.0A\include;
C:\Program Files\Microsoft SDKs\Windows\v6.0A\include;
Other Includes:
Stable Source Directories:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\atlmfc\src\mfc;
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\crt\src;
Here's the option I choose when installing:
--
Rick C. Hodgin
PS -- Fantasque Sans Mono is the best programming font (https://www.programmingfonts.org/ and a no ligatures version is here: https://github.com/spinda/fantasque-sans-ligatures/releases). Liberation Mono is a close second because the bold text of its font is so much more pronounced than the non-bold text. It really punches on older font renders like those from the Windows XP / Server 2003 era. Of course, this is all just my opinion. I could be wrong. :-) |
Edited by - foxmuldr on Nov 19 2024 1:07:52 PM |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 19 2024 : 12:56:48 PM
|
I have been able to verify that enabling VA and launching VS 2022 comes up with the GitHub Copilot and feedback icons hidden. Disabling VA and launching VS 2022 comes up with the icons visible. I am able to do this in succession repeatedly.
Microsoft has asked me to send them a dump file of the devenv.exe process with the hidden icon condition (right-click the process in task manager, create dump file). We'll see what comes of it.
--
Rick C. Hodgin
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 20 2024 : 12:13:30 PM
|
If you have the time, can you try installing VA into the test profile, as I explained above? If you have any problems with the instructions I can try to explain more fully.
I have VS2008 installed here as well, and am not seeing the problem. So I doubt that is the trigger. |
zen is the art of being at one with the two'ness |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 20 2024 : 4:20:29 PM
|
I did. I gave you the results of installing it as you indicated. See the "Posted - Nov 15 2024 : 4:59:38 PM" comment. Might be different in your timezone, but it begins with:
productPath: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
displayName: Visual Studio Professional 2022
installationVersion: 17.12.35506.116
The command I used to run (d:\downloads\vax\): ...
It came up: VSIX Installer ...
To launch: ...
I told it to uninstall Visual Assist upon exit. Exited. It uninstalled. Re-ran the launch command again: ...
It then shows the icons returned, along with the [VATEST] label, which I've never seen before (that label / text in that area):
It's my comment with the two pictures showing the results when VA is installed and enabled, or uninstalled, with the VATEST user.
--
Rick C. Hodgin
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 21 2024 : 08:19:41 AM
|
Apologies, I missed that reply.
The "VATEST" marker is normal when running in a test profile. It's something newer versions of Visual Studio do, which helps you keep track of what is happening when you are working with more than one profile.
It is odd you had to uninstall and reinstall VA in the test profile to fix this, but it does tell us that its a profile specific problem. Normally this means either an interaction problem with another extension you have installed in your default profile, or there is a problem with the settings in the default profile.
If you open both the test profile and your default profile, and compare the list in:
IDE tools menu -> Extensions and Updates...
do you have the same extensions installed in both profiles? Obviously, given the tests you have run, your version of VA will probably be different.
If the list of extensions is the same, can you please try exporting your IDE settings from your default profile, and then importing them into your test profile. You can export them via:
IDE tools menu -> Import and Export Settings -> Export selected environment settings
and the import is in the same dialog.
I doubt that this will have any effect on the problem, but it is the next sensible test to try. |
zen is the art of being at one with the two'ness |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 21 2024 : 09:19:04 AM
|
My IDE exhibited the same behavior on my profile, and on the VATEST profile. When VA's installed and enabled the icons are missing. When VA's uninstalled or disabled the icons are present. It seems to be a system-wide VA thing that's unrelated to a profile, other than the profile has VA installed and enabled to make the issue appear. But since it happens on both profiles, it does not seem to be profile specific at all. Am I missing something?
I have not had any other extensions installed except VA. Only the ones that come installed and enabled by default in a new VS install. Here's the full list of installed extensions:
Azure Data Lake and Stream Analytics Tools
Live Share 2022
Microsoft Library Manager
ML.NET Model Builder 2022
Test Adapter for Boost.Test
Test Adapter for Google Test
Visual Assist
Workflow Manager Activities
I later installed these two, and it's doing the same thing with them installed:
ClaudiaIDE -- Change the background of the editor window
ChatGPTExtension -- Access to ChatGPT from inside Visual Studio
--
Rick C. Hodgin
|
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 21 2024 : 09:22:48 AM
|
Microsoft replied with this comment on the Developer Community post:
"The dumps show the controls are missing entirely in the bad case, not just hidden, so the next step is to determine why the controls are not created. We have logging for failure when creating the frame controls, so can you get into the bad state, then launch devenv from the commandline with the /log switch. That'll enable the logging and should capture any frame control failures. Once repro'd go to %appdata%\Microsoft\VisualStudio\17.0_xxxxxxxx and upload the ActivityLog.xml file to the ticket. Thanks!"
I ran with /log, and uploaded the ActivityLog.xml file. I can send it to you as well if you'd like. Here's a reference to Visual Assist I found in it:
<entry>
<record>257</record>
<time>2024/11/21 14:23:38.915</time>
<type>Error</type>
<source>Editor or Editor Extension</source>
<description>System.NullReferenceException: Object reference not set to an instance of an object.#x000D;#x000A;
at WholeTomatoSoftware.VisualAssist.Classification.f.n(String ext)#x000D;#x000A;
at WholeTomatoSoftware.VisualAssist.Classification.f.p(IVsTextBuffer A_0)#x000D;#x000A;
at WholeTomatoSoftware.VisualAssist.Classification.f.VsTextViewCreated(IVsTextView textViewAdapter)#x000D;#x000A;
at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call)</description>
</entry>
--
Rick C. Hodgin
*feline edited to word wrap* |
Edited by - feline on Nov 22 2024 07:42:22 AM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 22 2024 : 11:03:41 AM
|
Clearly something is going wrong, and its happening across several builds of VA, so its not as simple a bug in one version of VA.
Going back over your VA about information, it says Windows 8.0
I cannot get Visual Studio 2022 to install under Windows 8.1, since the OS is to old for this version of Visual Studio. The installer reports "Visual Studio wasn't designed to work with this version of Windows. Please upgrade to a supported operating system."
Following the workarounds and system requirements link in the message, I am told:
>> Windows 8 and Windows Server 2012
>> Visual Studio 2022 doesn't install on Windows 8 and Windows Server 2012.
Is VA reporting your version of Windows correctly? |
zen is the art of being at one with the two'ness |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 23 2024 : 10:26:10 AM
|
Yes. It's an up to date Windows 10 install. If you ever catch me running Windows 8 or 8.1, know I have been replaced vis-a-vis Invasion Of The Body Snatchers.
--
Rick C. Hodgin
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 25 2024 : 08:18:21 AM
|
Strange that the OS is being reported wrong. Still, that makes it a lot easier to test here. This isn't a problem I am seeing on any of my Windows 10 machines.
Can you please try loading the Visual Studio Installer, and on the entry for VS2022, use the "More" button to open a pull down list. On this pull down list can you please use "Export configuration". This will save out a text file listing the components of VS2022 that you have installed.
Can you please send me this configuration file, along with your IDE and VA settings. I can then install VS2022 with the same components selected, and import your settings, and see if this will let me reproduce the problem you are seeing. I am not confident it will show the problem, but its certainly worth a try.
Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up. |
zen is the art of being at one with the two'ness |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 26 2024 : 1:25:02 PM
|
I went into VAssistX - Visual Assist Options - Performance - Export, and created a .REG file with my settings. And then Visual Studio's Tools - Export and created the .vssettings file with my settings. And then Visual Studio Installer and created the .vsconfig with my settings, all three of which I've sent you in email in a .7z file.
The archive password is: VisualAssistXUserSince2006!!
--
Rick C. Hodgin
|
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 26 2024 : 1:29:41 PM
|
:-)
--
Rick C. Hodgin
|
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 27 2024 : 08:42:29 AM
|
I took the password off the file, and sent it as a ZIP file with slightly different text. It appears to have gone through. I got a reply with Case 165218 indicated.
--
Rick C. Hodgin
|
|
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Nov 27 2024 : 12:18:36 PM
|
I have the files now, thank you for these. Rather surprisingly, installing your configuration, and then importing your settings, along with installing VA 2537 was enough, I am now seeing the problem here!
Now I want to try and find out why, and if it is a settings related problem or not. |
zen is the art of being at one with the two'ness |
|
|
|
foxmuldr
Tomato Guru
USA
416 Posts |
Posted - Nov 27 2024 : 12:22:00 PM
|
Wonderful!
--
Rick C. Hodgin
|
|
|
| |
Topic |
|
Losing GitHub Copilot and feedback icons
