Debugging CppCustomVisualizer doesn't work in VS2019 about concordextensibilitysamples

[gregg-miskelly]

Thanks for opening this. I enhanced the documentation by adding this section: https://github.com/microsoft/ConcordExtensibilitySamples/wiki/Cpp-Custom-Visualizer-Sample#if-debug-launch-doesnt-start-visual-studio-correctly

[pps83]

When I open clean checkout debug of vsix looks like on your screenshot. After running it once, it changes to what I have. Regardless, if I start it for the first time, or if I force /rootsuffix Exp $(SolutionDir)\TargetApp\TargetApp.sln (or /rootsuffix Exp $(SolutionDir)TargetApp\TargetApp.sln) I get identical behavior: new instance of VS starts and shows dialog to load project/solution and even if I load TargetApp manually in that new VS instance I don't get visualizer working.

[pps83]

I figured it out why it didn't work for me. I use awesome Smart Command Line Arguments extension by @MBulli and this extension clears/resets default Command Arguments string with an empty string. That's clearly a bug in SmartCommandlineArgs. When I set /rootsuffix Exp $(SolutionDir)\TargetApp\TargetApp.sln in command args windows (part of Smart Command Line Arguments extension) for vsix project, then everything work. Thanks for your help and sorry for taking your time!

I filled an issue in SmartCommandlineArgs instead