Quote:
You need to reference the ADODB Primary InterOp Assembly instead, which
gets around this problem. (Or at least you do with VB'2003). |
Hello Phill,
1.)
I tried that with References to ADODB 2.7. That works - fine.
I read, VS2005 uses PIA automatically, while adding an reference,
instead of creating a new interop-assembly, if a PIA is registered for
that dll.
==================================
2.)
Microsoft KB says that for ADODB 2.8, there is no PIA . (
http://support.microsoft.com/?scid=k...696&x=14&y=14).
-----------------------
Issue 7: You experience problems working with components that expect
ADO 2.8 interfaces
The ADODB PIA that is included with Visual Studio 2005 is the same
component that was included with Visual Studio .NET 2003 and was built
by using the Microsoft .NET Framework 1.1. The ADODB PIA was built to
interact with ADO 2.7 interfaces and has not been updated to work with
ADO 2.8 interfaces.
Therefore, attempts to use the ADODB PIA together with components that
expose ADO 2.8 interfaces will fail. This scenario is not supported
with the ADODB PIA.
-----------------
======================
3.)
Any idea for ADODB 2.8 ? ( we don't want to change ADODB version ) ?
4.)
What do you think about that workaround:
- Project B references the ADODB 2.8 ( VS2005 creates
Interop.Assembly )
- Project A references the Interop.ADODB assembly in obj/Debug/ folder
Thx & Greetings
Gordian