The story for deploying code is not something that MS has done very well.

For VBA code you would have to either export the module the code is in and
then import it on each computer or copy the entire VbaProject.OTM file
(where the VBA lives). Doing that will overwrite any macros the users
already have. Importing a module can't be scripted that I know of.

For any managed code addin you have to get the security right, among other
things. You can use a VSTO addin but you have to follow the deployment
walkthrough almost word for word and you would need a separate VSTO addin
for Outlook 2003 and for 2007 and your 2003 addin would require Office 2003
Professional or above.

If you want to do Ribbon support for Outlook your options are limited to a
managed shared addin or VSTO addin or an addin in unmanaged code using VB6
or Delphi or C++ or something like that.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Todd Walton" wrote in message
ups.com...
On Jul 12, 1:11 pm, "Ken Slovak - [MVP - Outlook]"
wrote:
Is this just for yourself? If so go with a VBA macro. If it's for
distribution then VBA is not the way to go.

It is for distribution. Is it really that hard to distribute VBA? I
have control of all machines. Could I not script installing it?

Deploying VSTO addins can be done but is a bear to get everything exactly
right

So, I distributing a VBA macro is much too difficult and distributing
a VSTO addin is very difficult.

VBA cannot be used for Outlook ribbon code.

Oh. I figured I'd be able to add to the ribbon a button that runs a
macro. Hmm...

-todd