Choosing a Visual Basic project type

When you decide to create custom functionality for Meridian Enterprise using Visual Basic programming, you have several options. In most cases, we recommend you extend the functionality of the standard Meridian Enterprise applications by creating an interface extension. Visual Basic interface extension programming involves creating functions and commands that are integrated into the user interface of the Meridian Enterprise clients (PowerUser or Configurator). For example, you may create your own property pages to hold custom property values for a document, folder, or work area. Or, you may want to create your own revision mechanism or custom workflow.

You may also choose to create a custom client application that runs stand-alone. A stand-alone client can, for example, examine all working copy documents in a Meridian Enterprise vault and present a sorted list to a manager. Client programming could also be a Visual Basic for Applications macro inside Microsoft Word or AutoCAD that queries Meridian Enterprise for information related to an open document and performs some tasks in the document based upon those results, for example.

Included with the Meridian Enterprise Developer Edition are templates for several different types of Visual Basic projects. The templates help you to quickly create the basic framework for different types of projects by referencing the necessary Meridian Enterprise type libraries, setting the project type, and creating initial project forms and code. Each template is useful for different purposes. You need to choose one of the templates, depending on the kind of functionality you want to develop.

The project types are:

• AMM Extension Project: An extension to the user interface of the Meridian Enterprise PowerUser or Configurator that can include process automation, business logic, and user commands. This project type suits the majority of programming needs. For example, an interface extension can contain custom properties and property pages, commands, and event handling. This project type produces an ActiveX dynamic link library (DLL) that must be registered with Configurator in the vault where it will be used by a system administrator. The ActiveX DLL will run in-process with the client application. The DLL can be deployed to the client computers on demand when packaged as an Internet Package (CAB) file.
• AMM Project: A stand-alone application capable of accessing Meridian Enterprise vaults, subject to the same security and licensing enforcement as the other Meridian Enterprise clients. The same techniques can also be used with Visual Basic for Applications from inside other applications. Produces a standard 32-bit executable that can be run from within Windows.
• AMM Menu Extension: Adds a custom command to the Tools menu of the PowerUser client. This project type produces an ActiveX dynamic link library (DLL) that must be registered with Configurator in the vault where it will be used by a system administrator. The ActiveX DLL will run in-process with the client application.
• AMM Task Project: A class that extends server-side automation performed by the Meridian Enterprise Task Server. For more information on using the Task Server, see the Task Server Administrator’s Guide appendix in the Meridian Enterprise Administrator’s Guide. This project type produces an ActiveX dynamic link library (DLL) that must be registered on the computer running the Task Server by a system administrator. The ActiveX DLL will run in-process with the Task Server.

Related information

Creating a new interface extension

About AMM Menu Extension projects

About AMM Project projects

Accessing a vault from Visual Basic for Applications

Deploying an interface extension