SAMPLE: Comaddin.exe Office 2000 COM Add-In Written in Visual C++

ID: Q230689

The information in this article applies to:

SUMMARY

Comaddin.exe is a self-extracting executable that demonstrates building an Office 2000 Component Object Model (COM) add-in in Visual C++. A COM add-in is an in-process COM server (DLL) specifically designed to run within the context of one or more Office 2000 applications. COM add-ins provide a flexible, efficient, and uniform method of extending the Office 2000 environment.

COM add-ins are a new feature of Office 2000. They are built using any programming language that can create COM components, such as Visual Basic, Visual C++, Visual J++, and the Office 2000 Developer Edition of Microsoft Visual Basic for Applications.

This sample demonstrates the necessary steps to build a COM add-in in Visual C++. The sample creates a basic add-in shell that you can extend to build your own Office add-in.


MORE INFORMATION

The following file is available for download from the Microsoft Software Library:

Comaddin.exe
Release Date: Jan-04-1999

For more information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:
Q119591 How to Obtain Microsoft Support Files from Online Services


Comaddin.exe extracts the following files to a folder of your choosing: 

   FileName                    Size
   ----------------------------------------
   
   TestAddin.dsw               541 bytes
   TestAddin.dsp               4.11 KB 
   ComAddin.h                  6.19 KB
   ComAddin.cpp                8.38 KB
   ComAddin.def                205 bytes
   MyAddin.cpp                 10.6 KB
   MyAddinCF.cpp               2.18 KB
   BttnHandler.cpp             6.27 KB

IDTExensibility2

For a COM object to be an Office 2000 add-in, it must support the IDTExensibility2 interface as described in the Microsoft Add-In Designer Type Library (Msaddndr.dll). This interface has been declared for you in ComAddin.h so no import is necessary. All COM add-ins inherit from this interface and must implement each of its five methods:
When a COM add-in is first loaded, a QueryInterface call is made for IDTExtensibility2. If this call fails, the add-in is unloaded. If the call succeeds, the host application will use the reference returned to notify the add-in of changes made to its state. A description of each method follows.

OnConnection

The OnConnection event fires whenever the COM add-in is connected. The add-in may be connected on startup, by the end user, or through automation. If OnConnection returns S_OK, the add-in is said to be loaded. If any other value is returned, the host application will immediately release its reference to the add-in and the object will be destroyed.

OnConnection takes the following four parameters:

OnDisconnection

The OnDisconnection event fires when the COM add-in is disconnected and just before it unloads from memory. The add-in should perform any cleanup of resources in this event, and restore any changes made to the host application.

OnDisconnection takes the following two parameters:


OnAddInsUpdate

The OnAddInsUpdate event fires when the set of registered COM add-ins changes. In other words, whenever a COM add-in is installed or removed from the host application, this event fires.


OnStartupComplete and OnBeginShutdown

Both the OnStartupComplete and OnBeginShutdown events notify the add-in when the host application has left or is entering a state where user-interaction should be avoided because the application is busy loading or unloading itself from memory. OnStartupComplete will only fire if your add-in was connected during startup, and OnBeginShutdown will only fire if your add-in is disconnected by the host during shutdown.

Because the user-interface for the host application is fully active when these events fire, they may be the only way to perform certain actions that otherwise would be unavailable from OnConnection and OnDisconnection.

Registering the COM Add-In

In addition to normal COM registration, a COM add-in needs to register itself with each Office 2000 application in which it can safely run. To register itself with a particular application, the add-in creates a subkey, using its ProgID as the name for the key, under the following location:

HKEY_CURRENT_USER\Software\Microsoft\Office\<AppName>\Addins\<AddInProgID>
The add-in can provide values at this key location for both a friendly display name and a full description. In addition, the add-in should specify its desired load behavior using a DWORD value called "LoadBehavior." This value determines how the add-in will be loaded by the host application, and is made up of a combination of the following values:
The typical value specified is 0x03 (Connected | Bootload).

Add-ins that implement IDTExtensibility2 should also specify a DWORD value called "CommandLineSafe" to indicate whether they are safe for operations that do not support a user interface. A value of 0x00 means False, 0x01 is True. Because this sample displays a message box, it is not safe for command line execution, and therefore sets the value to 0x00.

Getting Started

To get started writing add-ins, compile the sample project, run regsvr32.exe on the built DLL, and then launch Microsoft Word, Excel, Powerpoint and/or Frontpage 2000. You should see a dialog box open as the add-in gets loaded that says "Hello" and tells you what application it is in.

(c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Richard R. Taylor, Microsoft Corporation.

Additional query words: 


Keywords          : kbfile kbsample kbAutomation kbExcel kbFrontPage kbVC kbPowerPt kbWord kbGrpDSO 
Version           : :2000; WINDOWS:2000; winnt:5.0,6.0
Platform          : WINDOWS winnt 
Issue type        : kbinfo

Last Reviewed: June 3, 1999