By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,846 Members | 1,709 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,846 IT Pros & Developers. It's quick & easy.

ADODB custom wrapper

P: n/a
We have a VB.NET project with a reference to ADO 2.5

When I open it on my machine, I get the following build error: "The
referenced component 'ADODB' has an updated custom wrapper available."

When I double click on it, I get the following dialog appear:

If I click 'No', for every object declared from the ADODB library, I get a
build error as follows: "Reference required to assembly 'ADODB' containing
the type 'ADODB.Connection'. Add one to your project."

If I click 'Yes', everything is fine on my machine but not on everyone elses
machine. They get build errors telling them that the wrapper needs to be
defined. The only way to get it to work on their machines is for them to
delete the ADODB reference and re add it. Then on my machine, I am back to
square one.

BTW: Our MDAC are running the same version and we don't want to use for now
ADODb .Net since we still have recordsets in our project.

Thanks in advance,
May 6 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Wonder,

Have you made your deployment package using a deployment project. That
should search for you all the dependencies and put that in the msi package.

I hope this helps,

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:7D**********************************@microsof t.com...
We have a VB.NET project with a reference to ADO 2.5

When I open it on my machine, I get the following build error: "The
referenced component 'ADODB' has an updated custom wrapper available."

When I double click on it, I get the following dialog appear:

If I click 'No', for every object declared from the ADODB library, I get a
build error as follows: "Reference required to assembly 'ADODB' containing
the type 'ADODB.Connection'. Add one to your project."

If I click 'Yes', everything is fine on my machine but not on everyone
elses
machine. They get build errors telling them that the wrapper needs to be
defined. The only way to get it to work on their machines is for them to
delete the ADODB reference and re add it. Then on my machine, I am back to
square one.

BTW: Our MDAC are running the same version and we don't want to use for
now
ADODb .Net since we still have recordsets in our project.

Thanks in advance,

May 6 '06 #2

P: n/a

Hi,

I don't get it why I should use the deployment package since we are
developing the app and the error happens when we open Vb.net; ADODB reference
shows up as missing.

The problem happens not when we install the app, but when we developers are
open the project in Vb.net
Thanks in advance.

"Cor Ligthert [MVP]" wrote:
Wonder,

Have you made your deployment package using a deployment project. That
should search for you all the dependencies and put that in the msi package.

I hope this helps,

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:7D**********************************@microsof t.com...
We have a VB.NET project with a reference to ADO 2.5

When I open it on my machine, I get the following build error: "The
referenced component 'ADODB' has an updated custom wrapper available."

When I double click on it, I get the following dialog appear:

If I click 'No', for every object declared from the ADODB library, I get a
build error as follows: "Reference required to assembly 'ADODB' containing
the type 'ADODB.Connection'. Add one to your project."

If I click 'Yes', everything is fine on my machine but not on everyone
elses
machine. They get build errors telling them that the wrapper needs to be
defined. The only way to get it to work on their machines is for them to
delete the ADODB reference and re add it. Then on my machine, I am back to
square one.

BTW: Our MDAC are running the same version and we don't want to use for
now
ADODb .Net since we still have recordsets in our project.

Thanks in advance,


May 6 '06 #3

P: n/a
Wonder,

than how do the developpers use the reference, it should just be a dll in
the section references.

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:03**********************************@microsof t.com...

Hi,

I don't get it why I should use the deployment package since we are
developing the app and the error happens when we open Vb.net; ADODB
reference
shows up as missing.

The problem happens not when we install the app, but when we developers
are
open the project in Vb.net
Thanks in advance.

"Cor Ligthert [MVP]" wrote:
Wonder,

Have you made your deployment package using a deployment project. That
should search for you all the dependencies and put that in the msi
package.

I hope this helps,

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:7D**********************************@microsof t.com...
> We have a VB.NET project with a reference to ADO 2.5
>
> When I open it on my machine, I get the following build error: "The
> referenced component 'ADODB' has an updated custom wrapper available."
>
> When I double click on it, I get the following dialog appear:
>
> If I click 'No', for every object declared from the ADODB library, I
> get a
> build error as follows: "Reference required to assembly 'ADODB'
> containing
> the type 'ADODB.Connection'. Add one to your project."
>
> If I click 'Yes', everything is fine on my machine but not on everyone
> elses
> machine. They get build errors telling them that the wrapper needs to
> be
> defined. The only way to get it to work on their machines is for them
> to
> delete the ADODB reference and re add it. Then on my machine, I am back
> to
> square one.
>
> BTW: Our MDAC are running the same version and we don't want to use for
> now
> ADODb .Net since we still have recordsets in our project.
>
> Thanks in advance,


May 6 '06 #4

P: n/a
The other developer does not have his ADODB 2.5 (Microsoft ActiveX...)
wrapper registered in his GAC (I shows that he has it, everything is the
same, but it shows Interop.Adodb, and on my machine with the same
functionality it shows up ADODB with a strong key name.
I don't know how I could force his computer to have ADODB registered wiith
a strong name, since it is already in the GAC and I can't remove it.


"Cor Ligthert [MVP]" wrote:
Wonder,

than how do the developpers use the reference, it should just be a dll in
the section references.

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:03**********************************@microsof t.com...

Hi,

I don't get it why I should use the deployment package since we are
developing the app and the error happens when we open Vb.net; ADODB
reference
shows up as missing.

The problem happens not when we install the app, but when we developers
are
open the project in Vb.net
Thanks in advance.

"Cor Ligthert [MVP]" wrote:
Wonder,

Have you made your deployment package using a deployment project. That
should search for you all the dependencies and put that in the msi
package.

I hope this helps,

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:7D**********************************@microsof t.com...
> We have a VB.NET project with a reference to ADO 2.5
>
> When I open it on my machine, I get the following build error: "The
> referenced component 'ADODB' has an updated custom wrapper available."
>
> When I double click on it, I get the following dialog appear:
>
> If I click 'No', for every object declared from the ADODB library, I
> get a
> build error as follows: "Reference required to assembly 'ADODB'
> containing
> the type 'ADODB.Connection'. Add one to your project."
>
> If I click 'Yes', everything is fine on my machine but not on everyone
> elses
> machine. They get build errors telling them that the wrapper needs to
> be
> defined. The only way to get it to work on their machines is for them
> to
> delete the ADODB reference and re add it. Then on my machine, I am back
> to
> square one.
>
> BTW: Our MDAC are running the same version and we don't want to use for
> now
> ADODb .Net since we still have recordsets in our project.
>
> Thanks in advance,


May 8 '06 #5

P: n/a
Regasm

http://msdn2.microsoft.com/en-us/library/tzat5yw6.aspx

I hope this helps,

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:26**********************************@microsof t.com...
The other developer does not have his ADODB 2.5 (Microsoft ActiveX...)
wrapper registered in his GAC (I shows that he has it, everything is the
same, but it shows Interop.Adodb, and on my machine with the same
functionality it shows up ADODB with a strong key name.
I don't know how I could force his computer to have ADODB registered wiith
a strong name, since it is already in the GAC and I can't remove it.


"Cor Ligthert [MVP]" wrote:
Wonder,

than how do the developpers use the reference, it should just be a dll in
the section references.

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:03**********************************@microsof t.com...
>
> Hi,
>
> I don't get it why I should use the deployment package since we are
> developing the app and the error happens when we open Vb.net; ADODB
> reference
> shows up as missing.
>
> The problem happens not when we install the app, but when we developers
> are
> open the project in Vb.net
>
>
> Thanks in advance.
>
>
>
> "Cor Ligthert [MVP]" wrote:
>
>> Wonder,
>>
>> Have you made your deployment package using a deployment project. That
>> should search for you all the dependencies and put that in the msi
>> package.
>>
>> I hope this helps,
>>
>> Cor
>>
>> "Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
>> news:7D**********************************@microsof t.com...
>> > We have a VB.NET project with a reference to ADO 2.5
>> >
>> > When I open it on my machine, I get the following build error: "The
>> > referenced component 'ADODB' has an updated custom wrapper
>> > available."
>> >
>> > When I double click on it, I get the following dialog appear:
>> >
>> > If I click 'No', for every object declared from the ADODB library, I
>> > get a
>> > build error as follows: "Reference required to assembly 'ADODB'
>> > containing
>> > the type 'ADODB.Connection'. Add one to your project."
>> >
>> > If I click 'Yes', everything is fine on my machine but not on
>> > everyone
>> > elses
>> > machine. They get build errors telling them that the wrapper needs
>> > to
>> > be
>> > defined. The only way to get it to work on their machines is for
>> > them
>> > to
>> > delete the ADODB reference and re add it. Then on my machine, I am
>> > back
>> > to
>> > square one.
>> >
>> > BTW: Our MDAC are running the same version and we don't want to use
>> > for
>> > now
>> > ADODb .Net since we still have recordsets in our project.
>> >
>> > Thanks in advance,
>>
>>
>>


May 8 '06 #6

P: n/a
That's the problem.

Thank you!
"Cor Ligthert [MVP]" wrote:
Regasm

http://msdn2.microsoft.com/en-us/library/tzat5yw6.aspx

I hope this helps,

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:26**********************************@microsof t.com...
The other developer does not have his ADODB 2.5 (Microsoft ActiveX...)
wrapper registered in his GAC (I shows that he has it, everything is the
same, but it shows Interop.Adodb, and on my machine with the same
functionality it shows up ADODB with a strong key name.
I don't know how I could force his computer to have ADODB registered wiith
a strong name, since it is already in the GAC and I can't remove it.


"Cor Ligthert [MVP]" wrote:
Wonder,

than how do the developpers use the reference, it should just be a dll in
the section references.

Cor

"Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
news:03**********************************@microsof t.com...
>
> Hi,
>
> I don't get it why I should use the deployment package since we are
> developing the app and the error happens when we open Vb.net; ADODB
> reference
> shows up as missing.
>
> The problem happens not when we install the app, but when we developers
> are
> open the project in Vb.net
>
>
> Thanks in advance.
>
>
>
> "Cor Ligthert [MVP]" wrote:
>
>> Wonder,
>>
>> Have you made your deployment package using a deployment project. That
>> should search for you all the dependencies and put that in the msi
>> package.
>>
>> I hope this helps,
>>
>> Cor
>>
>> "Wonder" <Wo****@discussions.microsoft.com> schreef in bericht
>> news:7D**********************************@microsof t.com...
>> > We have a VB.NET project with a reference to ADO 2.5
>> >
>> > When I open it on my machine, I get the following build error: "The
>> > referenced component 'ADODB' has an updated custom wrapper
>> > available."
>> >
>> > When I double click on it, I get the following dialog appear:
>> >
>> > If I click 'No', for every object declared from the ADODB library, I
>> > get a
>> > build error as follows: "Reference required to assembly 'ADODB'
>> > containing
>> > the type 'ADODB.Connection'. Add one to your project."
>> >
>> > If I click 'Yes', everything is fine on my machine but not on
>> > everyone
>> > elses
>> > machine. They get build errors telling them that the wrapper needs
>> > to
>> > be
>> > defined. The only way to get it to work on their machines is for
>> > them
>> > to
>> > delete the ADODB reference and re add it. Then on my machine, I am
>> > back
>> > to
>> > square one.
>> >
>> > BTW: Our MDAC are running the same version and we don't want to use
>> > for
>> > now
>> > ADODb .Net since we still have recordsets in our project.
>> >
>> > Thanks in advance,
>>
>>
>>


May 8 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.