J
Jim Black
When I try to run the sample code ("OfficeCalendar") from Section 5.4 of
Andrew Whitechapel's book ".NET Development For Microsoft Office" under the
VS2003 debugger, it always crashes as it is trying to load the COM Add-In.
This is a sample that brings up Excel, loads the OfficeCalendar COM Add-In,
and then connects to the COM Add-in. When I press F5 to debug it in VS2003,
it builds the COM Add-In and launches Excel. Within a very short period of
time, however, Excel goes away and the COM Add-In is placed on the blacklist.
Here's what else I know:
(1) It never makes it to the Connect method. It must be failing as Excel
tries to load the COM Add-in.
(2) If I run Excel outside of the debugger, everything works just fine. The
very same COM Add-In loads and connects and does what it is supposed to do.
This means that the registry settings and assemblies are not the problem.
(4) It runs just fine on a second development machine. One major difference
between my two development machines is that I've installed VS2005 on the
machine where the failure occurs.
This problem looks very much to me like a configuration problem on my
machine, and I suspect that it was caused by my attempt to have both VS2003
and VS2005 on the same machine. What could it be? I have removed VS2005
and have repaired the installation of VS2003, but neither changed the
behavior. The only thing I haven't done yet is to totally remove VS2003 and
reinstall it from scratch.
Any ideas before I take this drastic step?
--- Jim Black
Andrew Whitechapel's book ".NET Development For Microsoft Office" under the
VS2003 debugger, it always crashes as it is trying to load the COM Add-In.
This is a sample that brings up Excel, loads the OfficeCalendar COM Add-In,
and then connects to the COM Add-in. When I press F5 to debug it in VS2003,
it builds the COM Add-In and launches Excel. Within a very short period of
time, however, Excel goes away and the COM Add-In is placed on the blacklist.
Here's what else I know:
(1) It never makes it to the Connect method. It must be failing as Excel
tries to load the COM Add-in.
(2) If I run Excel outside of the debugger, everything works just fine. The
very same COM Add-In loads and connects and does what it is supposed to do.
This means that the registry settings and assemblies are not the problem.
(4) It runs just fine on a second development machine. One major difference
between my two development machines is that I've installed VS2005 on the
machine where the failure occurs.
This problem looks very much to me like a configuration problem on my
machine, and I suspect that it was caused by my attempt to have both VS2003
and VS2005 on the same machine. What could it be? I have removed VS2005
and have repaired the installation of VS2003, but neither changed the
behavior. The only thing I haven't done yet is to totally remove VS2003 and
reinstall it from scratch.
Any ideas before I take this drastic step?
--- Jim Black