Jump to content

Recommended Posts

Posted

I'm doing a lot of remote debugging lately, and I'm having problems when debugging an app that throws an exception during startup. I can attach a remote debugger to a running process, but then I'll miss the errors in the beginning. I would like the ability to start a new process already attached.

 

Is this possible with the VS2005 remote debugger as-is? If not, is it possible to build some sort of bootstrapper that can run, attach the debugger and then launch my own app? Process.Start won't do since it'll launch a new, unattached process. I was thinking of doing Assembly.Load() for my EXE and looking for the static void Main() to run, but that seems overcomplicated.

 

Am I missing something trivial here?

 

More...

 

View All Our Microsoft Related Feeds

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...