Interop.ADODB created...why?

Hi,

I'm a VB.net developer that works for a small consulting company. We
work together with our customers to develop software to fit their
needs.

Anyhow...

When anyone in our office adds a reference to ADODB, an interop is not
created. If we add from the .NET tab in references, the managed
assembly is used. If we add from the COM tab, the Primary Interop
Assembly is used.

However, when our customer adds a reference, Interop.ADODB is created.

This creates havoc when we go back in to make changes for them or they
for us because the ADODB resolution cascades down through the other
referenced DLLs in the project, so, in an emergency when they have to
fix something we created, EVERYTHING in the project that uses ADODB
must be recompiled...the same happens if we need to fix something they
created.

We've contacted MS on the issue and been told that this is a bug in
the .net framework itself...but there must be someway to resolve
this...

Is there a way to force .net to use ADODB from the GAC or at least the
PIA's? Even when our customer points to these versions, an Interop is
created.

Please help!

Thanks,

Kevin Matthews
matthews (at) consultassoc (dot) com
.

Relevant Pages

  • Re: Using early-bound interface on a late-bound object
    ... > the compiler determines which interfaces to use, ... > supports the declared interface. ... >> help if someone can point me to some authoritative document or reference ... within customer shops when they mirrored this 'division' to keep their ...
    (microsoft.public.vb.general.discussion)
  • RE: ObjectDataSource in ASP.NET 2.0
    ... For datasourcecontrol and databindig control, ... it don't quite makesense to maintain such a in-memory reference. ... again from orginal datasource, e.g: ... | Customer customer = new Customer; ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Java collections
    ... location in memory for the Customer that was referenced by the Customer ... And the garbage collection would know ... `Customer c' means that c is a *reference* to a Customer, ... there is only one Customer instance in play, ...
    (comp.lang.java.programmer)
  • Re: Java collections
    ... location in memory for the Customer that was referenced by the Customer ... And the garbage collection would know ... `Customer c' means that c is a *reference* to a Customer, ... there is only one Customer instance in play, ...
    (comp.lang.java.programmer)
  • Re: Wish I was using .net
    ... a reference to an ADODB.Connection object. ... Yes but unfortunately the customer got the error not the programmer or ... there would be zero chance of it getting to the customer. ... specify an enum value on its own without prefixing it with the enum name, ...
    (microsoft.public.vb.general.discussion)