Comments
2 comments
-
Hi Stefan,
I thought about that when I was putting that in.
There is another way to start an executable, by making a dummy project, and configuring it's debug tab to start something up (in which case of course you have full control ove command line parameters). I just added the Debug an Executable option as a shortcut for the mainline case.
I'm worried adding an extra prompt would slow the process down for more people than would be helped.
Perhaps we can give some tip to use the dummy project method somehow?
What do you think?
A -
Hi,
Thanks for the swift answer.
Make sense, but you need to create a dummy project for each small thing that you want to debug.
I've just created a small wrapper that is starting up anything (params to it are exe-path & collection of params).
Works well for me ;-)
But the dummy project is a better way to go...
In fact - maybe it would be to users benefit to propose to save down a new solution for every new debug session?
--
Cheers
Stefan
Add comment
Please sign in to leave a comment.
Would it be able to add a parameter to provide a set of command-line parameters to a executable, which will be debugged?
--
Cheers,
Stefan