The only problem that I have seen is that it is a little bit slower to step through code while debugging. If that is a problem, which debuggers are attached could easily be a configuration option. For example, we could also attach T-SQL, Script or Workflow debugging engines. It will be very obvious in the code.
Also, I wrote it so that if it has trouble using the EnvDTE80 interfaces, it will fall back to managed only debugging using the old interfaces. I have attached the patch to issue #431. Thanks. Rob Prouse -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Brown Sent: April-22-09 3:10 PM To: [email protected] Subject: MbUnit Re: Native Debugging Please open up an issue and attach the patch. That way I won't forget to apply it! Do you think there could be any problems with attaching the Native debugger all of the time? I've had it go a little nuts on me before although mainly during remote debugging sessions. Thanks! Jeff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rob Prouse Sent: Wednesday, April 22, 2009 11:49 AM To: [email protected] Subject: MbUnit Native Debugging Some of our test suites call into Native code, but we cannot step into the native code when using the new debug command line or button in Icarus. I have a patch for Gallio.VisualStudio.Interop.VisualStudioDebugger that attaches the Managed and Native debuggers using EnvDTE80 instead of EnvDTE. Should I open an issue and add the patch, or is this such an isolated case that this feature shouldn't be added? Thanks. Rob Prouse --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
