dotnet interop:
I have that problem too..Basically my debugger as well as my add-in
crashes when i installed framework 2.0 on my machine.
I use it in a similar situation, where i have a C++ excel shim and a
dotnet assembly that provides the UI for my add-in.
Once i installed .NET 2.0, then my VS2003 debugger would try to load
the 2.0 framework libraries, and would promptly crash.
In your case, i think what is happenning is that Excel may be loading
the newer version of the framework (not just mscoree.dll which will
always be the latest one) but all of the managed assemblies as well.
One way to figure out whether this is happenning is to look in the
output information of the debugger to see what versions of the dlls it
is loading.Another is to download Sysinternals (I guess its
Microsofts's now :-)) Process Explorer and see what versions of the
dlls are being loaded by Excel.
On Jan 25, 2:29 pm, "William DePalo [MVP VC++]"
[quoted text, click to view] <willd.no.s...@mvps.org> wrote:
> "L-E Eriksson" <L...@nospam.com> wrote in messagenews:OIaXsqJQHHA.140@TK2MSFTNGP04.phx.gbl...
>
>
>
>
>
> > I have a vb.NET dll that I use from Excel. From Excel the functions in the
> > dll is called. This works and has done so for a long time.
>
> > But what has stopped working is debugging. After changing computer I
> > can't debug calls from Excel to the component. Of course I have in the
> > property pages for the dll checked the box "Start External Program" and
> > pointed out Excel.exe.
> > - I have also set the projects output path to the folder of excel.exe.
> > - The "Generate debugging info" checkbox is checked as well.
> > - The pdb is generated and is located in the same folder as the dll.
>
> > When I run the project, excel is starting. But on the very first call to
> > the .NET component, excel.exe is terminated and execution stops, without
> > error message.
>
> > Note: Debugging in this scenario worked for several years, before changing
> > computer.I can't say for certain that it is your problem, but recently a native
> application of mine that loads the CLR and some managed components into it
> just ceased to be debuggable with VS2003. It turns out I was paying the
> price for having installed a new version of the framework on the machine.
>
> If the machine you had been using only had v1.x of the framework, and if the
> new one has a more recent version of the framework as well, you might want
> to read this post
>
>
http://blogs.msdn.com/jmstall/archive/2005/12/05/VS2003_crashes_with_... >
> for the workaround.
>
> Regards,
> Will
>
>
www.ivrforbeginners.com- Hide quoted text -- Show quoted text -
