This documentation is archived and is not being maintained.

Development Environments

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

To develop applications using the Microsoft Office Communicator Automation API, the following requirements must be met:

  • Microsoft Office Communicator 2007 is installed on your development machine.
  • Microsoft Office Communicator 2007 SDK is installed on the development machine. The SDK is available for download from MSDN.

Be sure to add references of the CommunicatorAPI and CommunicatorPrivate namespaces to your application project. The following is the instructions to do so using the Microsoft® Visual Studio® development system.

To add CommunicatorAPI and CommunicatorPrivate namespaces
  1. In the Solution Explorer, highlight the References node under the project of your application.

    Bb787231.fa96fdf6-eb76-4900-8d33-372de60c8222(en-us,office.12).gif
  2. Click Add Reference to open the Add Reference dialog box.

    Bb787231.85c92294-a8b3-461b-9753-38064d64b0e2(en-us,office.12).gif
  3. On the COM tab, select the Microsoft Office Communicator 2007 API Type Library entry, and then click OK.

    Microsoft Office Communicator 2007 Private Type Library can be selected if IMessengerPrivate interface and the related dispinterfaces (for events) are to be used.

Be sure to include in your application project all the required header files as listed as follows:

  • windows.h: this is the header file for the commonly used Win32 API including COM library functions.
  • tchar.h: this header file is needed to use the _TCHAR type.
  • msgrua.h: this is the header file for the basic API entities of the Communicator Automation API.
  • msgrua_i.c: this file contains the definition of the named interface and class IDs for the interfaces and cocreateable classes defined in the msgrua.h file. You can also generate this file using the MIDL compiler to compile the msgrua.idl file.
  • msgrpriv.h: Inclusion of this header file is required only if the IMessengerPrivate interface and the related dispinterfaces (for events) are to be used.
  • Msgrpriv_i.c: this file contains the definition of the named interface and class IDs for the interfaces and cocreateable classes defined in the msgrpriv.h file. You can also generate this file using the MIDL compiler to compile the msgrpriv.idl file.

For Scripting

Scripts need to supply Communicator.UIAutomation when creating the Microsoft ActiveX® object for Communicator. For an example in JavaScript, see Object Instantiation.

For reasons of security, limitations are imposed to block scripts from accessing certain interfaces, invoking some interface members, or catching some events. Some restrictions of this kind apply to scripts running from a Web page, but not to scripts running on a local computer (for example, using the Windows Script Host environment). Such limitations are documented in Office Communicator Automation API Reference.

To deploy a custom application that implements the Office Communicator API, you must include CommunicatorAPI.dll and CommunicatorPrivate.dll in the installation routine you create for your custom application. These two assemblies are installed locally in the same directory that your custom application is installed. Note that these dll files must not be installed in a Global Assembly Cache (GAC).

Show: