how to produce O2002 compatible addin from O2003 development workstation?

  • Thread starter Thread starter matro
  • Start date Start date
M

matro

hi there,

I just upgraded from Outlook 2002 (XP) to Office Outlook 2003; once
recompiled my com addin, I noticed it can only work with O2003.

the issue is I don't know how to compile it for O2002: I tried to copy
the required msoutl.olb version 10 and set the vb references to it and
to the microsoft shared\office 10\mso.dll, but the dll still wants
O2003 to operate.

fortunately the opposite is true: if I compile the addin on a
workstation with O2002 installed, it will work on a computer with
O2003 installed (even if it was a clean install, not an upgrade).

however, I'd like to use one development workstation only: the one
with O2003.

can you help?

--------

Francesco "Matro" Martire

available at www.realpopup.it:
RealPopup, the freeware winpopup replacer
RealAccount, freeware plugin for MS Outlook XP
MaTreo, freeware frontscreen for your Treo and PalmOS devices
 
If you want to develop for more than one version of Outlook you must
develop using the oldest version you want to support. In your case
that would be Outlook 2002.

Many of us use virtual machines to handle things like that. You can
set up a VM for Outlook 2002 and develop on that and still have your
main setup be Outlook 2003. See www.vmware.com for one supplier of VM
software that a lot of us use.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Lead Author, Professional Outlook 2000 Programming, Wrox Press
Lead Author, Beginning VB 6 Application Development, Wrox Press
Attachment Options
http://www.slovaktech.com/attachmentoptions.htm
Extended Reminders
http://www.slovaktech.com/extendedreminders.htm
 
If you want to develop for more than one version of Outlook you must
develop using the oldest version you want to support. In your case
that would be Outlook 2002.
Click to expand...

ok; I finally discovered I can work on a workstation which had Outlook
2002 then upgraded to Office Outlook 2003.

basically, two references are needed:

C:\Program Files\Microsoft Office\Office10\MSOUTL.OLB and
C:\Program Files\Common Files\Microsoft Shared\Office10\mso.dll

when you upgrade to O2003, the first file is deleted, but you can
easily take it from another machine (or make a copy before the
upgrade).

I tested resultine dll against clean machines with WinME+O2002,
Win2000+O2002 and Win2000+O2003 with success.
Many of us use virtual machines to handle things like that. You can
set up a VM for Outlook 2002 and develop on that and still have your
main setup be Outlook 2003. See www.vmware.com for one supplier of VM
software that a lot of us use.
Click to expand...

I'm a fan of vmWare since early dates, it's good to see I'm not alone.
:-)

--------

Francesco "Matro" Martire

available at www.realpopup.it:
RealPopup, the freeware winpopup replacer
RealAccount, freeware plugin for MS Outlook XP
MaTreo, freeware frontscreen for your Treo and PalmOS devices
 
I wouldn't have 2 different versions of the Outlook libraries
registered on one machine, that can lead to all sorts of problems that
can be very hard to trace down. If you use VMWare just create a VM
with whatever version of Outlook and OS you want and use that as the
dev platform.
 
I wouldn't have 2 different versions of the Outlook libraries
registered on one machine, that can lead to all sorts of problems that
can be very hard to trace down. If you use VMWare just create a VM
with whatever version of Outlook and OS you want and use that as the
dev platform.
Click to expand...

that's overall good, however, as far as I've understood, outlook COM
interfaces are registered side-by-side, so there are no direct issues
with versioning; the original problem was caused by setup/uninstall
routines.


--------

Francesco "Matro" Martire

available at www.realpopup.it:
RealPopup, the freeware winpopup replacer
RealAccount, freeware plugin for MS Outlook XP
MaTreo, freeware frontscreen for your Treo and PalmOS devices
 
Back
Top