compilation error: The type is defined in an assembly that is not referenced

[Omatase]

Here is my code:

CDO.Message iMessage = new CDO.MessageClas s();

string sFrom; string sDate;

iMessage.DataSo urce.Open(bstrU RLItem,null,
ADODB.ConnectMo deEnum.adModeRe ad,
ADODB.RecordCre ateOptionsEnum. adFailIfNotExis ts,
ADODB.RecordOpe nOptionsEnum.ad OpenSource,""," ");

Here is the compilation error:

The type 'ADODB.ConnectM odeEnum' is defined in an assembly that is not
referenced. You must add a reference to assembly 'ADODB,
Version=7.0.330 0.0, Culture=neutral ,
PublicKeyToken= b03f5f7f11d50a3 a'. C:\Documents and
Settings\davidb r\My
Documents\Visua l Studio
2005\Projects\I nformXY\InformX Y\ExchangeEvent Sink.cs 45 25
InformXY

the error comes from argument number 3 on line:

iMessage.DataSo urce.Open(bstrU RLItem,null,
ADODB.ConnectMo deEnum.adModeRe ad,
ADODB.RecordCre ateOptionsEnum. adFailIfNotExis ts,
ADODB.RecordOpe nOptionsEnum.ad OpenSource,""," ");

I get a similar error on the 4th and 5th arguments.

Here are some things I have tried that didn't work:

couldn't cast to ADODB.ConnectMo deEnum
couldn't use corresponding integer values

I am using C# 2.0. I copied the code directly from a project that works

fine in 1.1. I created interop dlls using tlbimp on some exchange dlls.

The iMessage object was instantiated from a namespace derived from one
dll and the enums wer in another. My only working idea is that I need
to make these interop dlls out of compatible versions of original
exchange dlls.

I imagine there may be a work around I can use here to tell it to use
the code as is even though it comes from a different assembly or to
force it to just use the integer counterparts for the enum values.

[Dave Sexton]

Hi Omatase,

See if there are any PIA (Primary Interop Assemblies) available for the
application before importing your own.

If you must import your own assemblies you might want to try the tlbimp
utility with the /reference switch so that the generated assemblies
reference each other. You must generate the assemblies in the correct
order. If you generated the assemblies with the appropriate references and
still get the error you are probably still missing type libraries that need
to be imported.

The last option would be to ditch CDO and ADO as they are legacy components
in the context of .NET. The .NET Framework provide intrinsic classes to
handle mail and data access.

- Dave Sexton

<Om*****@gmail. comwrote in message
news:11******** **************@ 75g2000cwc.goog legroups.com...

Here is my code:

CDO.Message iMessage = new CDO.MessageClas s();

string sFrom; string sDate;

iMessage.DataSo urce.Open(bstrU RLItem,null,
ADODB.ConnectMo deEnum.adModeRe ad,
ADODB.RecordCre ateOptionsEnum. adFailIfNotExis ts,
ADODB.RecordOpe nOptionsEnum.ad OpenSource,""," ");

Here is the compilation error:

The type 'ADODB.ConnectM odeEnum' is defined in an assembly that is not
referenced. You must add a reference to assembly 'ADODB,
Version=7.0.330 0.0, Culture=neutral ,
PublicKeyToken= b03f5f7f11d50a3 a'. C:\Documents and
Settings\davidb r\My
Documents\Visua l Studio
2005\Projects\I nformXY\InformX Y\ExchangeEvent Sink.cs 45 25
InformXY

the error comes from argument number 3 on line:

iMessage.DataSo urce.Open(bstrU RLItem,null,
ADODB.ConnectMo deEnum.adModeRe ad,
ADODB.RecordCre ateOptionsEnum. adFailIfNotExis ts,
ADODB.RecordOpe nOptionsEnum.ad OpenSource,""," ");

I get a similar error on the 4th and 5th arguments.

Here are some things I have tried that didn't work:

couldn't cast to ADODB.ConnectMo deEnum
couldn't use corresponding integer values

I am using C# 2.0. I copied the code directly from a project that works

fine in 1.1. I created interop dlls using tlbimp on some exchange dlls.

The iMessage object was instantiated from a namespace derived from one
dll and the enums wer in another. My only working idea is that I need
to make these interop dlls out of compatible versions of original
exchange dlls.

I imagine there may be a work around I can use here to tell it to use
the code as is even though it comes from a different assembly or to
force it to just use the integer counterparts for the enum values.