By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,779 Members | 1,498 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,779 IT Pros & Developers. It's quick & easy.

Remote Debugging

P: n/a
I am attempting to remote debug a process (C# application) whose execution
time is less than 2 seconds. When attempting to attach this process from
the client machine, I am unable to catch the process in time.

Any suggestions on how to fix this issue? I understand once the process is
attached I can set my breakpoints, the only problem is that the process I am
attaching to runs so quickly I am not able to attach to it.

Thanks
Nov 15 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I had to face the same kind of problem.
I defined a key in my config file that is used to place the process in sleep
mode after it started (eg: TimeToSleepAfterStart: 60s)

So, In my code, I execute a Thread.Sleep() if the value read from the config
file is greater than 0.

José
"chris fink" <ch********@decisionone.com> a écrit dans le message de
news:ec**************@TK2MSFTNGP12.phx.gbl...
I am attempting to remote debug a process (C# application) whose execution
time is less than 2 seconds. When attempting to attach this process from
the client machine, I am unable to catch the process in time.

Any suggestions on how to fix this issue? I understand once the process is attached I can set my breakpoints, the only problem is that the process I am attaching to runs so quickly I am not able to attach to it.

Thanks

Nov 15 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.