| T O P I C R E V I E W |
| Alan Baljeu |
Posted - Sep 04 2024 : 4:59:13 PM
Hi folks,
One of our engineers has finished analyzing the dumps sent in. (thank you for those!) The source of the message boxes is an InvalidOperation exception being thrown by the Visual Assist extension. The error code text being displayed matches the message written by Whole Tomato in the exception (see image below). The error code associated with the exception is 0x80131509 which is interpreted as �An operation is not legal in the current state�, but VS will prioritize showing the exception�s message over the error code�s message.
You can share this callstack with Whole Tomato:
License: Standard ([email protected] / JDFK-FRAEHE-EPW9FK-32ND) Support ends 2023.01.12
VA_X64.dll file version 10.9.2463.0 built 2022.10.25
DevEnv.exe version 17.11.35219.272 Community
msenv.dll version 17.0.35125.118
Comctl32.dll version 6.10.22621.3672
Windows 11 11.0 23H2 Build 22631
24 processors (x86-64)
Language info: 65001, 0x409
Platform: Project defined
Stable Includes:
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\Community\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\Community\VC\Auxiliary\VS\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\atlmfc\include;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\include;
Other Includes:
Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.22621.0\ucrt;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\src;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\atlmfc\src\mfc;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\atlmfc\src\mfc;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\crt\src;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\atlmfc\src\atl;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\atlmfc\src\mfcm;
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\atlmfc\src\mfc;
|
| 2 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Sep 05 2024 : 09:30:20 AM
VA 2500 is the first version to load in VS2022 version 17.7.0 and above without throwing an error. I am actually surprised you are not getting the same error on start up with this combination of versions.
Since you are using an earlier version of Visual Assist on a much newer version of Visual Studio 2022, I suspect you are running into a related, or even the same issue.
Microsoft changed Visual Studio 2022 as the versions went on, and this required matching changes in Visual Assist, for us to still work correctly. |
| Alan Baljeu |
Posted - Sep 04 2024 : 5:03:45 PM
Additional info: this message pops up every time I press Esc in a document. It doesn't start immediately, but does shortly after I start working in a document window. If I were to Extensions Disable Visual Assist, Visual Studio would crash. |
|
|
