Possible Duplicate:
Debugging a C# executable that crashes on launch
Does anyone have a good trick other than
Thread.Sleep(10000);
to attach the remote debugger to process that crashes almost immediately?
Can you start the process with WinDbg and hand it off somehow? I tried this but the process was grayed out and I couldn’t hand it off to a different debugger. (My VS2008 in this case)
See this MSDN page: http://msdn.microsoft.com/en-us/library/ff678494.aspx
More specifically, section Launching a remote process