Debugging across applications

[Andrew Ducker]

I have an application that has to take numerous different command line
options. I wrote an app launcher to call into it (by creating a
process, setting the filename/arguments and then starting it).

However, while my debugging goes into the app launcher, it doesn't
follow into the application itself. Is there any way to make it do so,
other than attaching to the process once its running (which is
incredibly slow).

Cheers,

Andy D

 

[Tom Porterfield]

I have an application that has to take numerous different command line
options. I wrote an app launcher to call into it (by creating a
process, setting the filename/arguments and then starting it).

However, while my debugging goes into the app launcher, it doesn't
follow into the application itself. Is there any way to make it do so,
other than attaching to the process once its running (which is
incredibly slow).

You can set command line parameters to be used while debugging your
application. Go to the project properties for your application,
Configuration Properties, Debugging. There you can specify command line
arguments under the start options.

 

[Andrew Ducker]

You can set command line parameters to be used while debugging your
application. Go to the project properties for your application,
Configuration Properties, Debugging. There you can specify command line
arguments under the start options.

Cheers Tom. I know I _can_ do this, but when the command line
parameters can vary a lot and I have big list of different ones for
recreating different situations, I don't find this terribly efficient.
I really need something to allow me to pick and choose different
command line options, or at least choose from the last n ones that I
used.

Andy

 

[Brian]

Is it possible to add a DEBUG region in the startup of your program, and
in that region, read a configuration file?

In that way, you could have 30 different configuration files for the
variety of command line arguments, and you could prompt yourself to
choose a config file at startup (or you could put it in the command line
args in VS)

It just seems to me that if there are that many arguments, maybe a
configuration file might help.

--Brian