[Timo]

I have tried the new build and am happy to report that the issue has mostly been resolved.

• The first time i opened the project, i got the same STA error message and hanging IDE, but every other time afterwards it opened fine, including after another uninstall and reinstall to provoke the error. I’ll chalk that up to some leftover temp files from the old version.
• The error appears to be fixed completely. I was unable to reproduce it in this version among any of my company projects or the multiple test projects i made. VS Intellisense also works properly again in all cases i tried.
• the VcxprojReader.exe instances are mostly fixed, but every now and then, they do still stick around after closing VS and prevent file movement as they used to. From my cursory tests, it seems relatively rare (a good dozen of openings/closings before it shows up), and i see no pattern in when it happens either. I have had it happen and not happen in all of my affected company and test projects. Considering i have trouble reproducing it even when im trying, i’d say the odds of it ever being noticed in actual usage are slim to none, so im happy as is, but if you want to investigate further, i will also assist to the best of my abilities.

Thanks for your quick support and build, greatly appreciate it 👍

[Timo]

Thank you for the build. Unfortunately, it made the problem significantly worse; now, when opening a project with the error, i get one popup error message reading

—————————
Error
—————————
The calling thread must be STA, because many UI components require this.
—————————
OK
—————————

For every affected project in the solution (thats 3 popus at once in our company project), and then visual studio hangs indefinitely on the Loading Project dialog, so i never even get to open the project (even the cancel button does not work).

Of course i would much prefer to use VS IntelliSense over Clang IntelliSense if at all possible;

for once because, as you mentioned, clangs navigate to definition indexes the entire project (which takes about 10 seconds), and does so every time you change even a single letter in the project, which makes it practically unusable while editing code and literally slower than just scrolling there yourself if you only use it once,

but also because clang intellisense seems actively hostile towards templates; there is no autocomplete (whereas intellisense offers autocomplete for types of your choosing or automatically when you use concepts), and in fact actively hinders you from just writing template <typename T> by autocompleting the T to a random known identifier for some reason.

That being said, the error mentioned also happens with cmake projects using clang intellisense. While, in this case, it does not actively prevent anything from working, it still floods the output in error messages, and it still leaves behind instances of vcxprojreader.exe that have to be killed with a task manager if you want to for example to a git checkout afterwards. Not a deal breaker, but something i would like to solve it possible.

[Timo]

I have been able to reproduce it on newly created empty projects.

It seems to happen every time when a solution contains a visualgdb project in a subfolder of the .sln file, as opposed to the default location of putting it next to the sln.

It happens to me with multiple types (i tried a linux and an embedded STM project), with multiple different build systems (tried MSBuild and Cmake).

It also leaves a VcxprojReader.exe instance in the process list that does not exit after i close Visual Studio and seems to have some file open, preventing deletion of the folder until you kill it manually.

Im on VisualGDB version 6.1R3 (build 5547) and Visual Studio Professional 2022 Version 17.14.18 (October 2025) and Visual Studio Professional 2022 Version 17.14.40 (i updated after noticing my VS was older than my VisualGDB build, but the bug persisted in the new version).

Since this is a company wide project over which i do not have complete control, changing project structure is unfortunately not an option. Would be thrilled if there are other things i could try, otherwise i will have to learn to live with it i guess.

[Timo]

I went the .vcxproj file route. Worked like a charm!

For Posterity:

I added a conditional property group

<PropertyGroup Condition=”‘$(DesignTimeBuild)’!=””>

<IntelliSenseCommandline>/Zc:__cplusplus</IntelliSenseCommandline>

</PropertyGroup>

Then i added the value of the property to the AdditionalOptions line

<AdditionalOptions>-x c++ -fconcepts $(IntelliSenseCommandline) %(AdditionalOptions)</AdditionalOptions>

Now it compiles and highlights correctly!

Thank you for the quick support.

[Timo]

Hi,

I copied the LanguageStandard attribute from a regular project and it worked like a charm.

It even keeps the tags when you change project settings.

Thank you very much for the swift assistance😃

[Timo]

Sorry for that, didn’t realize i was out of support. Should be renewed now.

I would very much like to go ahead and try.

[Timo]

Im on VS 17.9.6.

I created a Win32 Project, and the syntax highlighting worked as expected.

I also created a different VisualGDB project (this time for an ARM-Based device), and the same problem appeared.

[Author]

Posts