Re: Building VB.NET Interface definitions from a COM interface
- From: Rob Perkins <rperkins@xxxxxxx>
- Date: Wed, 22 Mar 2006 13:42:23 -0800
No no, I'm aware of those. However, I discovered a circular reference situation which makes me uncomfortable where I have a COM DLL containing four COM interfaces, one of which is referenced by my .NET assembly.
By that I mean that the COM DLL references an interface on the .NET assembly.
The .NET assembly, in turn, references the interfaces on the COM DLL. It has not failed to work, but it has made debugging... interesting.
The .NET assembly in turn references *different* interfaces on the COM DLL.
Rob
.
- References:
- Building VB.NET Interface definitions from a COM interface
- From: Rob Perkins
- Re: Building VB.NET Interface definitions from a COM interface
- From: Tom Shelton
- Re: Building VB.NET Interface definitions from a COM interface
- From: Rob Perkins
- Building VB.NET Interface definitions from a COM interface
- Prev by Date: Re: AddressOf from VB6 to .Net VB
- Next by Date: Re: Modify a CSV file
- Previous by thread: Re: Building VB.NET Interface definitions from a COM interface
- Next by thread: Re: Moving/deleting the DB upon close
- Index(es):
Relevant Pages
|