Command line fails to update when starting with F10

[krilbe]

If a debug session is started with F5, the command line seems to be properly set according to the SmartCommandlineArgs settings, but not if the debug session is started with F10 (Step over).

I have not tested F11 etc. You probably should check all possible ways to start a debug session.

Tested with VS 2017 community on a C# .NET Framework 4.7.1 console application.

[MBulli]

Well the problem is that we're not aware of any event which just tells us if the program is started. I can handle the StepOver/StepIn Commands etc. but I also need to know if the program is already been debugged.

[krilbe]

Alright, I understand. Not so easy to fix then. I can live with it. :-)

[MBulli]

Still we try to fix it ;)