| T O P I C R E V I E W |
| MythTitans |
Posted - Dec 20 2024 : 09:30:52 AM
Hello,
I just upgraded to Visual Studio 17.12.3 and also wanted to upgrade Visual Assist as well but I am getting an error message "A critical error occurred while initializing Visual Assist." and Visual Studio closes after a few seconds.
I tried reinstalling Visual Studio completly but it didn't fix the problem, so tried downgrading Visual Assist version from 2024.8, and the first that worked without error is 2024.1.
Does anyone know what could be the problem ?
Thanks. |
| 2 L A T E S T R E P L I E S (Newest First) |
| MythTitans |
Posted - Dec 21 2024 : 07:53:45 AM
Thank you for you answer.
I followed the steps and I get the same error when running the VATest profile, and Visual Studio closes (or crashes ?) right after that. |
| feline |
Posted - Dec 20 2024 : 10:15:40 AM
Not a problem I have seen or heard of.
The fact that this is effecting so many versions of VA is really worrying. My first guess is a problem with your default profile / install, but this is just a guess.
To test this, can you please try installing VA into a test profile. To do this, first 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.
Hopefully this is clear and easy to follow. Does the test profile load successfully with a working VA? |
|
|
