Loose coupling of COM in C# or How to avoid COMException 0x80040154
Posted
by user283318
on Stack Overflow
See other posts from Stack Overflow
or by user283318
Published on 2010-03-15T23:46:47Z
Indexed on
2010/03/15
23:49 UTC
Read the original article
Hit count: 662
I have a .Net 2 C# application I am developing which uses a VB 6 generated COM DLL. The VB DLL is updated frequently any my application crashes with a System.Runtime.InteropServices.COMException (0x80040154). The part of the COM DLL I use does not change but the version (and CLSID) will.
The "Specific Version" option for the reference is false. The WrapperTool is tlbimp.
How do I tell my application not to worry about changes in the DLL? Is there any way of checking just the functions I am using?
© Stack Overflow or respective owner