Can't debug VS.NET 2003 COM server application after installing VS 2005 RC

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jeff Brown - 29 Sep 2005 20:18 GMT

I've developed a C# class library that runs as an in-process COM server
within a VB6 application.

I developed my library with VS.NET 2003, and it must continue to be
developed on that platform for the foreseeable future.

Yesterday, for a completely unrelated purpose, I downloaded and installed VS
2005 RC.

However, now, I can no longer debug my C# COM library from within VS.NET
2003! My library still builds okay; and it still runs okay OUTSIDE of VS.
But, I can no longer debug it from within VS! (When I try, my VB6 test
program simply opens and then immediately closes.)

Does anyone have any idea how I can restore the debuggability of my C# COM
library? Otherwise, I guess I'll just have to uninstall VS 2005 RC...
bummer!

Thanks,
Jeff Brown

Reply to this Message

Christopher G. Carnahan - 01 Nov 2005 22:47 GMT

I have this problem now the RTM versions. I can't use VS 2003 to debug
managed code running in IIS. It tells me that the process I am trying to
attach to is not running any managed code, when I know it is. I haven't
changed anything in the project or my environment. All I've done is install
VS 2005.

- Christopher

> I've developed a C# class library that runs as an in-process COM server
> within a VB6 application.
[quoted text clipped - 16 lines]
> Thanks,
> Jeff Brown

Reply to this Message

Can't debug VS.NET 2003 COM server application after installing VS 2005 RC

Free Magazines