Issue with unmanaged C++ code calling into unmanaged VB.NET assembly
- From: "Tim DeMarco" <tdemarco391@xxxxxxxxx>
- Date: 9 Jul 2005 09:02:11 -0700
Hi All,
I need help with a .NET COM Interop issue.
I have a .NET assembly (a single DLL with classes written in VB.NET )
that I register for COM interoperability using Visual Studio. An
unmanaged C++ application #imports the .tlb of this .NET assembly.
Everything is built and it runs fine. We have associated GUIDs to each
of the classes that are used by the C++ client application.
If a change is made to the .NET Assembly (not changing interfaces) and
I rebuild it and then I overwrite the old DLL with the new one and
re-register using regasm /Codebase , the C++ client application crashes
when its run. I must re-build the C++ application using the .tlb file
generated from the latest .NET assembly DLL before it will work again.
I should not have to rebuild the client application to get it to work
properly if no interfaces have changed.
Any advice would be appreciated.
Thanks
Tim DeMarco
.
- Follow-Ups:
- Re: Issue with unmanaged C++ code calling into unmanaged VB.NET assembly
- From: Johannes Passing
- Re: Issue with unmanaged C++ code calling into unmanaged VB.NET assembly
- From: Tim DeMarco
- Re: Issue with unmanaged C++ code calling into unmanaged VB.NET assembly
- Prev by Date: RE: Outlook addin and IWin32Window
- Next by Date: Re: Issue with unmanaged C++ code calling into unmanaged VB.NET assembly
- Previous by thread: Outlook addin and IWin32Window
- Next by thread: Re: Issue with unmanaged C++ code calling into unmanaged VB.NET assembly
- Index(es):
Relevant Pages
|