Rank: Advanced Member Groups: Member
Joined: 10/4/2016 Posts: 104
|
Hi,
Would you be aware of "an easy way" to resolve conflict on RemoteDebugPort when debugging multiple browser executables?
As you know each browser executable must use a different RemoteDebugPort value otherwise as soon as one has opened a debug session, if any other executable attempts to do the same on the same port, it now gets a connection refused which would not have happened if it had opened that debug window first.
Since one cannot change the port number of an already opened form for a given process, before I start looking at using the registry for instance as a way for all my processes to register which port they intend to use for debug if needed (which implies a tedious cleanup management), I was wondering if there was a way to determine which value has been assigned to Runtime.DefaultEngineOptions.RemoteDebugPort within each wrapper process from another process?
Thank you!
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,218
|
Hi,
No. There is no built-in support for this. You will have to work this out yourself. :)
Thanks
|