How do I package a version-independent COM AddIn?

[TonyJollans]

Hi All,

I've posted in the VB Forum and got no response. Do any of you here know this?

I have created a COM AddIn for Outlook 2000 using VB6, and it works - no problem so far. I now want to give it to someone else who has Outlook XP. I have no reason to think it won't work under XP but I don't know how to package it.

The project has references to Office 2K files, MSO9.DLL and MSOUTL9.OLB. I haven't included them in my package for testing because I have them on my target machine. As I understand it the XP target will have later equivalents (MSO.DLL & MSOUTL.OLB) which I shouldn't need to include in the package but which I presume I need the project to reference.

What, if anything special, do I have to do to make my project version-independent? If it helps I have access to the Office 2003 files (but not the XP ones).

Enjoy,
Tony

--------------------------------------------------------------------------------------------
We want to help you; help us to do it by reading this: Before you ask a question.
Excel VBA Training and more Help at [url=http://www.vbaexpress.

 

[PHV]

Use late binding and so your COM addin don't need references.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[TonyJollans]

Thanks, PH, but it isn't an option as far as I understand how it works.

I might be able to use late binding on the Outlook objects but I need early binding to use Office CommandBarButton Events.

Enjoy,
Tony

--------------------------------------------------------------------------------------------
We want to help you; help us to do it by reading this: Before you ask a question.
Excel VBA Training and more Help at [url=http://www.vbaexpress.