1 person found this helpful
An "application" that is a set of applications should be designed in a way
that each individual application can be independently tested. You could:
1) Design the child such that the child can be launched first and will wait
for communication from the startup app
2) Launch the child app via NavigateToURL and put all communications on the
url so you can just put the url params in the run/debug settings for the
3) Make sure there is a way to delay the launch of the child app. That way
you can "run" the startup app, then tell the debugger you are going to debug
an external app before launching the child.
I have used (3), but I use the command line debugger (fdb) to do it.
Option 1 isn't really an option in my case.
Option 2 - that's how it currently works. The problem is, some of these parameters are different every time.
Option 3 - I cannot say I fully understand what exactly you mean by "tell the debugger you are going to debug an external app", but I'll try to read some documentation on fdb tommorrow, so thank you for this hint!
I thought there was a way to debug external just like you can profile
external. I can't find it.
There is also:
4) Export the first app as a release build and run it. Then it won't try
for the debugger and the child should be the first to connect to the