********************************************************************************
                   MS Office Delphi sample add-in README
********************************************************************************

1) General
MSOAddIn is skeleton implementation (and framework) of MS Office COM add-in.
It provides implementation of required COM add-in functionality, and can be
used as base for Office add-in development - all "grunt" tasks are handled by
this implementation, you must only dig into Office application's object model
to develop functionality you need.

MSOAddIn enables user to create new contact in Outlook and insert contact info
into Word or Excel documents as part of it's sample functionality.

2) Supported MS Office versions
MS Office 2000 and MS Office XP supported. MSOAddIn is 3 add-ins:
Outlook, Excel and Word addins.

3) Compilation
Project has conditional define - 'DEBUG', which controls messages output into
debug console using OutpuDebugString() function. You can alter this define in
project options.

MSOAddIn is Delphi 5 project, but you can compile it in Delphi 6-7 without
problems.

4) Installation
To install MSOAddIn register it either from IDE or using regsvr32.exe.
Run Outlook, Excel or Word - you'll see new toolbar with button created
by MSOAddIn. This method usefull when no user interaction required.

Office applications offers COM add-in manager, which are not in application's
menus by default.

To insert COM add-in manager into application's menus perform following:
- Open "Customize" options dialog ( 'Tools->Customize' from menus)
- Go to "Commands" tab
- From "Categories" list select "Tools" item
- From "Commands" list locate "COM Add-ins..." command and drag it to desired
  position in menus.

COM add-in manager used for installation (click "Add" button and locate
MSOAddIn.dll to install it), removal and enabling/disabling.

5) Uninstallation
To uninstall MSOAddIn unregister it either from IDE or using regsvr32.exe or
remove it from application's COM add-in manager.

6) Known issues
Command bars created by MSOAddIn are not removed from Office application
when MSOAddIn removed via COM unregistration (unregistered from IDE or using
regsvr32.exe), remove them manually.

7) Developing your add-ins
MSOAddIn skeleton implementation is also a simple framework, which enables you
to create your own add-in in few steps:

- Start new ActiveX Library project
- Add to project MSOAddIn's core units: EventSink.pas, MSOEventSink.pas,
  MSOfficeAddIn.pas and MSOAddIn_Utils.pas
- Add object model import units for office application of your choice:
  Word_TLB.pas, Outlook_TLB.pas or Excel_TLB.pas (with
  addition of Office_TLB.pas and VBIDE_TLB.pas) or import them yourself from
  available Office type libraries (Project->Import Type Library) into project
  folder (or your preffered 'imports' folder).
- Add new Automation Object to project - it will be your add-in.
- Change Automation Object inheritance from TAutoObject to TMSOfficeAddIn
- Replace class factory to TMSOAddInFactory in initialization clause of
  new Automation Object unit (see OutlookAddIn_IMPL.pas how to code it).
- That's all, compile and register your add-in.

Knowledge of Office Object model is worhty during Office add-ins development.
You have resources on MSDN, but better approach - add VB help to your Office
application installation - ok, it's in VBA, but covers all apects of development
(better than MSDN).


8) Contact info

    Vadim Krochak
    vkrochak@bezeqint.net