I get "CmdArgsParser did not load correctly" dialog on one solution.

[BengtGustafsson]

This seems to be identical to #67 and I also see the text of #64 in the actual argument window.

I'm using your 3.1 version on VS 2022 17.9.6

Just as in #67 this only happens on one of my solutions which was open in VS when the computer was forcefully rebooted.

I deleted the json files in the build tree but that didn't help.

So it seems that some info in Microsoft's configuration files was corrupted or something like that.

[MBulli]

Besides the json file we store some data in the .suo file. Maybe that one ist corrupted?If you can reproduce the issue a log file would be nice to make the extension more robust in such cases.