| T O P I C R E V I E W |
| MrJones4u |
Posted - Apr 03 2025 : 03:34:59 AM
Hello,
just tried updating to build 2554 and found that after updating I was no longer able to start multiple instances of visual studio. VS will show the IDE window but will remain in hourglass indefinitely...
The first instance always works the second does not.
As this is the normal mode I work with I have had to downgrade back to build 2547.
cu,
Michael
Microsoft Visual Studio Enterprise 2022 (64-bit) - Version 17.12.5
|
| 6 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Apr 04 2025 : 07:47:56 AM
Thank you for the update, and I am glad this is now fixed.
I am not sure what to make of the problem though. If I had to guess, I would go with some odd process running in the background that was causing a problem for extra instances. We recently had to update our installer to better detect processes being left running by VS2022, so its not a stupid theory. But no idea why it didn't effect the first instance if that was the case.
Hopefully it won't come back, but obviously if it does, please do let us know. |
| MrJones4u |
Posted - Apr 04 2025 : 02:19:03 AM
They were started as pined solutions from the taskbar..
But, after reinstalling 2554 and rebooting, multiple instances are no longer an issue...
cu,
Michael
|
| feline |
Posted - Apr 03 2025 : 12:05:44 PM
OK, VS2022 Enterprise version 17.12.5 installed on a fully up to date Windows 11 machine. VA 2554.0 installed, both clean installs, so default settings.
I have loaded 4 instances, making a new solution in each instance.
It seems safe to say this isn't a general, all over problem.
How are you loading VS2022? Are you passing any command line parameters, or just loading it normally?
Assuming you are just loading it normally, a test profile is the next logical test.
To do this, can you first download the VS2022 specific installer for Visual Assist from:
https://downloadfiles.idera.com/WholeTomato/VA_X_Setup2554_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\Enterprise\Common7\IDE\devenv.exe
displayName: Visual Studio Enterprise 2022
installationVersion: 17.12.35728.132
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 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\Enterprise\Common7\IDE\VSIXInstaller.exe"
/appidinstallpath:"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\devenv.exe"
/skuName:Enterprise
/appidname:"Visual Studio Enterprise 2022"
/skuVersion:17.12.35728.132
/rootSuffix:"VATest" "C:\Users\%USERNAME%\Downloads\VA_X_Setup2554_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\Enterprise\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 with the test profile, or does this allow you to open 2 instances normally? |
| feline |
Posted - Apr 03 2025 : 09:42:53 AM
That really should not be a problem. The entire VA symbol database on my Unreal Engine test machine is 900gb. Unreal Engine is generally about as big as solutions people report using get, unless you are working on the entire Windows code base, or something else really massive. |
| MrJones4u |
Posted - Apr 03 2025 : 08:54:03 AM
Rebooting was sadly not an option yet, I'll test that when the next opportunity comes up.
As to drive space; C: is indeed running a bit low with only 668GB free... |
| feline |
Posted - Apr 03 2025 : 08:24:06 AM
No sign of any such problem so far here. I have tried both a Windows 10 and a Windows 11 machine. Windows 10 has VS2022 version 17.13.5, and I have opened 4 instances quite normally there.
The Windows 11 machine currently has VS2022 version 17.13.3, and I have again opened 4 instances there.
VA 2554 installed on both machines.
In case the version of VS2022 matters, I am going to install this exact version and re-run the test.
At the risk of asking a stupid question, have you tried rebooting yet? I would not expect this to matter, but you should not be seeing this problem either.
Are you short on hard drive space on C drive? Each instance of VA makes a separate VA symbol database, but these are normally relatively small, given the size of most hard drives. |
|
|
