Excel 2003 automation add-in Extensibility.dll deployment

[Andrew Wiles]

Hi

I have an automation add-in built using the IDTExtensibility2 interface.
When working with Office 2007 this addin installs and registers without
problems.

With Office 2003 the installation fails - RegAsm returns a message:

RegAsm : error RA0000 : Could not load file or assembly 'Extensibility,
Version=7.0.3300.0, Culture=nuetral, PublicKeyToken=b03f57f11d50a3a' or one
of its dependencies. Strong name validation failed. (Exceptio from HRESULT:
0x8013141A)

My understanding is that the Office 2007 Primary Interop installation
installs Extensibility.dll is in the GAC but that the Office 2003 PIA package
does not.

I have tried simply copying the Extensibility.dll to the install folder for
my project and this does not help.

What is the correct procedure for ensuring that the pre-requisites for an
automation add-in using IDTExtensibility2 are installed for Office 2003?

Thanks for any help

 

[Andrew Wiles]

But it is not a VSTO add-in??

Hi Andrew,


I think you'd better post this question in this group:

Public.vsnet.vstools.office.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

 

[Peter T]

But it is not a VSTO add-in??

What sort of addin is it

Regards,
Peter T

 

[Andrew Wiles]

Peter

It is a COM automation add-in using IDTExtensibility2 as the interface. I
know that some of the technology is shared with VSTO but I thought this was a
different class of application (Tell me if I'm wrong!)

 

[Peter T]

AFAIK all "Com" addins use the IDTExtensibility2 interface. But what
language and application was the addin written in.

Regards,
Peter T

 

[Andrew Wiles]

C#

AFAIK all "Com" addins use the IDTExtensibility2 interface. But what
language and application was the addin written in.

Regards,
Peter T

 

[Peter T]

I don't know C# but I believe you would have had to set a reference to
Office and Excel as you would in say VB6. If you compiled the addin with
those ref's set to Office & Excel 2007 try setting them to 2003.

Of course you'll need to do that in a system that has Office 2003 (2000/2
might also be OK).

Regards,
Peter T

 

[Andrew Wiles]

Thanks Jan

I will give the VSTO group a go

Hi Andrew,


Maybe bot, but the NG I pointed you to is visited by people who do Office AND
.NET development, which is a rare combination.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com