Home > Articles > Programming > Windows Programming

Through the Looking Glass: Debugging Hosted .NET Applications

  • Print
  • + Share This
When Oxford mathematician Charles Dodgson looked in the mirror, perhaps he saw Lewis Carroll. Carroll's genius was his ability to peer through the looking glass into the magical land called Wonderland. After a brief prelude, which spartanly demonstrates how to create a COM+ serviced component, Paul Kimmel shows you how to peer through the looking glass and debug .NET code that's hosted by another application.
Like this article? We recommend

Like this article? We recommend


If you're going to build enterprise solutions, some of your assemblies are bound to be hosted by other applications. A huge part of knowing how to code is having good debugging skills, but hosted assemblies can be challenging to debug unless you know that Visual Studio .NET supports debugging hosted applications by attaching to the host directly.

After a brief prelude that quickly demonstrates how to create a COM+ serviced component with .NET, I'll show you how to find and attach to the host and thereby permit tapping into and debugging your hosted assemblies. Whether you're debugging a DLL with NUnit, hosting an assembly in IIS, implementing COM+ components, or doing something else, this article will show you how any managed code can be debugged in Visual Studio .NET's integrated debugger.


I would like to dedicate this article to all of the Flip Bozo award recipients. You know who you are. Having both flipped the bozo bit and having it flipped on me has helped me to gain one more useful insight. To the academy, I say, thanks.

  • + Share This
  • 🔖 Save To Your Account