MBulli
I get "CmdArgsParser did not load correctly" dialog on one solution.
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.
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.
I have the same problem. I put the config into the .suo and directly loading a project with config stored in the .suo file fails. If I load a different project (without config) first and then switch the solution it works.
Attaching a debugger to VS while loading a solution gives me:
Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: 'The best overloaded method match for 'System.Collections.Generic.List<SmartCmdArgs.Logic.CmdArgumentJson>.Add(SmartCmdArgs.Logic.CmdArgumentJson)' has some invalid arguments'
in SmartCmdArgs17.dll!SmartCmdArgs.Helper.ProjectConfigHelper.GetVCProjEngineConfig.
If the config is loaded as part of package initialization then VS obviously complains about a failed InitializeAsync. I see that ProjectConfigHelper was removed in v2.6.1, so this might not be an issue anymore in the latest code.
FYI: in my case (v3.2.1), the 'CmdArgsPackage' error also started popping up after a reboot.
I found out a duplicate "Id" in the .args.json file, and removing that entry fixed the issue.
