Alex,
The type library is usually part of the DLL. There won't necessarily be a
separate tlb file (I don't know whether this is the case for CDO or not).
Use something like:
"d:\Program Files\Microsoft Visual Studio .NET\FrameworkSDK\Bin\TlbImp"
"D:\Current\YourCOMFile.dll" /keyfile:"YourKeyFile.snk"
/out:interop.YourFile.dll /namespace:interop.WhateverYouWant
Also, just in case you aren't aware, you will still need to make sure the
target PC has CDO and ADO are installed. The interops are just used to talk
to them - they don't 'replace' them.
Seeya
Matthew Wills @ MLC
Senior Analyst Programmer
|---------+---------------------------->
| | Alex Smotritsky |
| | <alex_smotritsky@|
| | YAHOO.COM> |
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: Re: [ADVANCED-DOTNET] com interop from a strongly named
assembly |
>--------------------------------------------------------------------------------------------------------------|
I've researched this and decided that generating my own interop for cdo is
a
can of worms I won't open -- unless I find it's type library. So does
anyone
have the type library or the PIA? Does anyone know of a .net email
component
that supports cdo fields when running against 1.0 of the framework?
-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew Wills
Sent: Wednesday, December 14, 2005 8:45 PM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] com interop from a strongly named assembly
Alex,
It looks like you are generating your own interops. For ADO, you should use
the PIA:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321688
I am not sure about CDO. If there isn't a PIA, you will need to generate
interops signed with your key (to make them strong named).
Seeya
Matthew Wills @ MLC
Senior Analyst Programmer
|---------+---------------------------->
| | Alex Smotritsky |
| | <alex_smotritsky@|
| | YAHOO.COM> |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------
-----------------------------------|
|
|
| To: [email protected]
|
| cc:
|
| Subject: [ADVANCED-DOTNET] com interop from a strongly named
assembly |
>---------------------------------------------------------------------------
-----------------------------------|
I'm trying to interop with CDO and ADODB from a strongly named assembly. I
get compile time errors saying:
Assembly generation failed -- Referenced assembly 'Interop.ADODB' does not
have a strong name
Assembly generation failed -- Referenced assembly 'Interop.CDO' does not
have a strong name
Looks like strongly named assemblies don't play well here. Any suggestions?
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
===================================
This list is hosted by DevelopMentorĀ® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
This e-mail is sent by or on behalf of the named sender identified above.
If:
(a) you do not wish to receive any e-mail marketing material from this
person in the future, please forward the contents of this email to
[EMAIL PROTECTED] with the word "unsubscribe" in the
subject box.
(b) you wish to unsubscribe from all central e-mail marketing lists
used by our business, please forward the contents of this e-mail to
[EMAIL PROTECTED] with the message "unsubscribe
from all central e-mail marketing lists" in the subject box.
If you do not forward the contents of this e-mail with your
unsubscription then it may not be able to be implemented.
The information contained in this e-mail communication may be
confidential. You should only read, disclose, re-transmit, copy,
distribute, act in reliance on or commercialise the information if you
are authorised to do so. If you are not the intended recipient of this
e-mail communication, please immediately notify us by e-mail to
[EMAIL PROTECTED], or reply by e-mail direct to the sender and then
destroy any electronic and paper copy of this message. Any views
expressed in this e-mail communication are those of the individual
sender, except where the sender specifically states them to be the views
of a member of the National Australia Bank Group of companies. Any
advice contained in this e-mail has been prepared without taking into
account your objectives, financial situation or needs. Before acting on
any advice in this e-mail, National Australia Bank Limited recommends
that you consider whether it is appropriate for your circumstances. If
this e-mail contains reference to any financial products, the National
recommends you consider the Product Disclosure Statement (PDS) or other
disclosure document before making any decisions regarding any products.
The National Australia Bank Group of companies does not represent,
warrant or guarantee that the integrity of this communication has been
maintained nor that the communication is free of errors, virus or
interference.
===================================
This list is hosted by DevelopMentorĀ® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com