More Adventures in .NET Land - Calling C# VS.NET Automation from VSIP

Another 2 days of banging my head aggainst the wall with mixing managed C# components together with ATL COM native components. As I said earlier, in part one, I have been working on trying to give myself and my team a productivity boost. I have been working on a full blown tool development environment fully integrated with Microsoft Visual C++.NET. As I said earlier, VSIP is extremely difficult to grok and work with. So I have been persuing a strategy of mixing VSIP with pieces of the VS.NET automation model to do some things like adding tools to the toolbox, menus, adding custom code, etc easier.

The big thing I ran into the last two days and got stuck on, is that I was not able to step into the managed C# assembly from the native ATL/C++ COM component in the debugger. I have the assembly in the GAC so I thought it was some weird issue. The .NET mailing list was unhelpful. I finally found the solution yesterday.

I guess I can't paste in an image here but the answer lies in Project - Configuration Properties - Debugging - Debuggers, which is usually set to Auto. I changed this to "Mixed" and it worked. It seems that Auto will do managd or unmanaged debugging but not both. Mixed combines both.

Last update: 6/26/2002; 8:56:22 AM.