Registering an interface extension

After packaging an interface extension, you must register it in the vault with the Meridian Enterprise Configurator.

Follow these steps to register an interface extension:

1. Open Meridian Enterprise Configurator and select the vault to which to register the extension.
2. On the Edit menu, select Register Extension. The Register Extension dialog appears.
3. Select the extension’s .CAB or .DLL file and click Open. The Register Extensions dialog appears.
4. By default, all extensions that are contained in the selected .CAB file are selected for registration. Clear the check boxes of any extensions that you do not want to register.
5. Click Register. The check mark in each check box changes to the letter R as each extension is registered to the vault.
6. Click Close when you are finished registering extensions

The Configurator will copy the extension to the BC-Meridian Extensions folder (AMM3EXT$ share) on the server. From there, any Meridian Enterprise client computer can download and install it when the extension is required.

After you have registered the extension, it will be listed in the Extensions branch of the of the configuration tree in Meridian Enterprise Configurator. If applicable, it will also appear in the Programs and Features list in Windows Vista (or higher) together with the other programs installed on the computer.

Note    To unregister an extension, see the Meridian Enterprise Configuration Guide.

Note    64-bit extensions might not load by 64-bit Meridian Enterprise client applications on some computers. If this occurs, and no error messages are shown, add the following DWORD registry value to every computer that will use the Meridian Enterprise 64-bit edition with .NET user interface extensions and set the data to 0:

HKEY_CURRENT_USER\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings\FlagsFor64bitExtensions

The property pages of the extension in Configurator display important information about the extension.

• Extension Type: Identifies the type of vault objects the extension can be applied to. This will be empty if you did not select an object type when creating the extension.
• Code Base: Contains the relative path where a client computer can find the .CAB or .DLL file of this interface extension. This path is relative to the BC-Meridian Extensions folder (AMM3EXT$ share) on the server.

Note    If, during testing, you registered an interface extension from the Visual Basic  IDE using the Register Extension button of the interface extension designer, the CodeBase property is not set. In this case, if you export the vault’s configuration to a .MET file, the interface extension’s files will not be included. Before deploying an interface extension in a production environment, you should always register all extensions through the Meridian Enterprise Configurator.

• File Revision: Contains the file version number of the extension’s .DLL file. You should take care to increment the version number before deploying new releases of your extensions as described in "Deploying an updated user interface extension."

Related information

Packaging an interface extension

Deploying an updated user interface extension