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

Interop.CDO uses Interop.ADODB which has a higher version...

P: n/a
Hi,

I have a C# assembly project under Visual Stuio 2008 Pro on Windows Server
2008. I converted the project from VS 2005.

The project references COM->Microsoft CDO for Windows 2000 Library 1.0,
which adds two entries under References called CDO and ADODB. When I compile
the solution, I get the following:

Error 1 Assembly 'Interop.CDO, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=13c3baacc352d1a9' uses 'Interop.ADODB, Version=6.0.0.0,
Culture=neutral, PublicKeyToken=13c3baacc352d1a9' which has a higher version
than referenced assembly 'Interop.ADODB, Version=2.8.0.0, Culture=neutral,
PublicKeyToken=13c3baacc352d1a9'
c:\sw\clweb\@tmp\Company.Web\release\Interop.CDO.d ll Company.Web

I tried to remove both CDO and ADODB from the references and add a reference
to "Microsoft CDO for Windows 2000 Library" again. This creates CDO and
ADODB under References and produces the same error.

How can I fix it?

Thank you,

John

Jun 27 '08 #1
Share this Question
Share on Google+
5 Replies


P: n/a
I tried removing ADODB from references and adding ADODB 2.8 and ADODB 6.0
without any luck.
"muriwai" <mu*****@nospam.nospamwrote in message
news:en**************@TK2MSFTNGP05.phx.gbl...
Hi,

I have a C# assembly project under Visual Stuio 2008 Pro on Windows Server
2008. I converted the project from VS 2005.

The project references COM->Microsoft CDO for Windows 2000 Library 1.0,
which adds two entries under References called CDO and ADODB. When I
compile the solution, I get the following:

Error 1 Assembly 'Interop.CDO, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=13c3baacc352d1a9' uses 'Interop.ADODB, Version=6.0.0.0,
Culture=neutral, PublicKeyToken=13c3baacc352d1a9' which has a higher
version than referenced assembly 'Interop.ADODB, Version=2.8.0.0,
Culture=neutral, PublicKeyToken=13c3baacc352d1a9'
c:\sw\clweb\@tmp\Company.Web\release\Interop.CDO.d ll Company.Web

I tried to remove both CDO and ADODB from the references and add a
reference to "Microsoft CDO for Windows 2000 Library" again. This creates
CDO and ADODB under References and produces the same error.

How can I fix it?

Thank you,

John
Jun 27 '08 #2

P: n/a
Hello John,

According to your description, you found your project failed on compiling
after converted from VS 2005 to VS 2008. The error message is "Interop.CDO
use Interop.ADODB 6.0.0.0 which has a higher version than referenced
assembly ADODB 2.8.0.0. If I misunderstood anything here, please don't
hesitate to correct me?

I'm not sure if you received this issue before you convert the project to VS
2008? This could help on verifying if this is a VS 2005 to VS 2008
conversion issue. Moreover, is it possible for you to create a new simple
project and add reference to CDO in VS 2008. We have to check if VS 2008
compile the project without error. This could help on confirm if this is VS
2008 issue.

This error means your project references to the wrong version of ADODB. The
current version is 2.8, but your CDO uses ADODB 6.0. It seems you have tried
to remove referenced assembly (ADODB 2.8), and added referenced assembly
(ADODB 6.0). Could you please also let me know the exact error message after
you changed referenced assembly?

Sorry for so many question. Actually, we haven't heard such issue so far.
Please understand we need detailed information to narrow down the issue.

If you have any more concern, please feel free to let us know. We are glad
to assist you.
Have a great day,
Best regards,
Wen Yuan
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support Engineer
within 1 business day is acceptable. Please note that each follow up
response may take approximately 2 business days as the support professional
working with you may need further investigation to reach the most efficient
resolution. The offering is not appropriate for situations that require
urgent, real-time or phone-based interactions or complex project analysis
and dump analysis issues. Issues of this nature are best handled working
with a dedicated Microsoft Support Engineer by contacting Microsoft Customer
Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jun 27 '08 #3

P: n/a
Hi Wen,

Thank you for your reply.

The issue did not exist in VS 2005 and showed up after conversion to VS
2008.

I manually deleted all the output and temp files ("Clean" and "Rebuild"
didn't help), re-referenced the CDO, and re-built the project. The problem
seems to have gone.

Cheers,

John

"Wen Yuan Wang [MSFT]" <v-******@online.microsoft.comwrote in message
news:eT*************@TK2MSFTNGP06.phx.gbl...
Hello John,

According to your description, you found your project failed on compiling
after converted from VS 2005 to VS 2008. The error message is "Interop.CDO
use Interop.ADODB 6.0.0.0 which has a higher version than referenced
assembly ADODB 2.8.0.0. If I misunderstood anything here, please don't
hesitate to correct me?

I'm not sure if you received this issue before you convert the project to
VS 2008? This could help on verifying if this is a VS 2005 to VS 2008
conversion issue. Moreover, is it possible for you to create a new simple
project and add reference to CDO in VS 2008. We have to check if VS 2008
compile the project without error. This could help on confirm if this is
VS 2008 issue.

This error means your project references to the wrong version of ADODB.
The current version is 2.8, but your CDO uses ADODB 6.0. It seems you have
tried to remove referenced assembly (ADODB 2.8), and added referenced
assembly (ADODB 6.0). Could you please also let me know the exact error
message after you changed referenced assembly?

Sorry for so many question. Actually, we haven't heard such issue so far.
Please understand we need detailed information to narrow down the issue.

If you have any more concern, please feel free to let us know. We are glad
to assist you.
Have a great day,
Best regards,
Wen Yuan
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
Jun 27 '08 #4

P: n/a
Hello John,
Thanks for your reply.

I'm really glad to hear you resolved the issue.
It seems VS 2005 IDE compiles the project with some old files which
generate by VS 2005. I think this maybe related with conversion.
Some temp files generated by VS 2005 confused VS 2008. Thereby, the issue
goes away after you clean the folder.
I believe the issue won't show up again. Anyway, if you find the issue come
back again, please feel free to let us know. We will follow up. It's my
pleasure to assist you.

Thanks again for your solution. Other community memebers may get benefit
from your reply.:)
Have a great day,
Best regards,
Wen Yuan

Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jun 27 '08 #5

P: n/a
Hello John,

This is Wen Yuan, again. Do you face the issue again? I just want to check
if there is anything we can help with.
Please feel free to let us know if you need further assistance. We are glad
to assist you.

Have a great day,
Best regards,
Wen Yuan

Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jun 27 '08 #6

This discussion thread is closed

Replies have been disabled for this discussion.