Share via

Servers: Implementing a Server

  • Article

|  Overview |  How Do I |  Sample |  Tutorial

This article explains the code AppWizard creates for a visual editing server application. If you are not using AppWizard, this article lists the areas where you must write code to implement a server application.

If you are using AppWizard to create a new server application, AppWizard provides a significant amount of server-specific code for you. If you are adding visual editing server functionality to an existing application, you must duplicate the code that AppWizard would have provided before adding the rest of the necessary server code.

The server code that AppWizard provides falls into several categories:

  • Defining server resources:

    • The menu resource used when the server is editing an embedded item in its own window.

    • The menu and toolbar resources used when the server is active in place.

    For more information on these resources, see the article Menus and Resources: Server Additions.

  • Defining an item class derived from COleServerItem. For further details on server items, see the article Servers: Server Items.

  • Changing the base class of the document class to COleServerDoc. For further details, see the article Servers: Implementing Server Documents.

  • Defining a frame-window class derived from COleIPFrameWnd. For further details, see the article Servers: Implementing In-Place Frame Windows.

  • Creating an entry for the server application in the Windows registration database and registering the new instance of the server with the OLE system. For information on this topic, see the article Registration.

  • Initializing and launching the server application. For information on this topic, see the article Registration.

For more information, see , , and in the Class Library Reference.

See Also   Containers, Menus and Resources (OLE), Registration