You can attach directly to IEXPLORE or IEEXEC and set breakpoints that way. (You'll have to attach manually) Or you can put an explicit System.Diagnostics.Debug.Debugger.Break() (or something like that) -- that works great.
-----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Shawn Wildermuth Sent: Tuesday, March 14, 2006 6:04 PM To: [email protected] Subject: [ADVANCED-DOTNET] Debugging IE Hosted WinForms Controls... I have some WinForms controls hosted in IE. They are successfully launching (so I am *not* debugging normal startup behavior with too few permissions) the controls in IE. I also have an ASP.NET 2.0 project in the same solution. What I want is to be able to launch the ASP.NET 2.0 project and if my WinForm control is launched, I want to be able to set breakpoints in it. Anyone figure this out? I've googled until my fingers bled. Thanks, Shawn Wildermuth <blocked::http://adoguy.com/> http://adoguy.com C# MVP, MCSD.NET, Author and Speaker =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
