I'm targeting 2000 and 2003 Server, if they don't have that out of the box I'll throw a fit.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, December 16, 2005 12:33 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] com interop from a strongly named assembly Alex, I believe so, yes. But you still need to make sure ADO and CDO are installed too. Seeya Matthew Wills @ MLC Senior Analyst Programmer (w) 02 9957 8183 (email) [EMAIL PROTECTED] |---------+-------------------------------------> | | Alex Smotritsky | | | <[EMAIL PROTECTED]| | | > | | | Sent by: "Discussion of | | | advanced .NET topics." | | | <[EMAIL PROTECTED]| | | EVELOP.COM> | | | | | | | | | 16/12/2005 16:21 | | | Please respond to | | | "Discussion of advanced | | | .NET topics." | | | | |---------+-------------------------------------> >--------------------------------------------------------------------------- -----------------------------------| | | | To: [email protected] | | cc: | | Subject: Re: [ADVANCED-DOTNET] com interop from a strongly named assembly | >--------------------------------------------------------------------------- -----------------------------------| If I get these interop dlls built and working with my existing dll, for deployment can I just throw these into the gac the way I do with my existing dll that's using these interop dlls? -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Wills Sent: Thursday, December 15, 2005 5:39 PM To: [email protected] Subject: Re: [ADVANCED-DOTNET] com interop from a strongly named assembly 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 list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ 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
