Deploying an updated user interface extension

When a Meridian Enterprise client application accesses an object to which an interface extension has been applied, it first checks to see if the extension version number registered in the vault is higher than that of the extension currently installed on the client computer. If it is higher, the extension’s .CAB or .DLL file is downloaded and installed on the client computer before the extension is activated. The extension will be installed in the C:\WINDOWS\Downloaded Program Files folder of the client computer. Dependent files will be installed to their appropriate locations. So in order to successfully deploy an updated extension, you must increase the file version number of the extension’s executable.

The file version number of an extension (and the assembly version number of a .NET assembly) consists of four elements. The format of the version number is: <MajorVersionNumber>.<MinorVersionNumber>.<BuildNumber>.<RevisionNumber>. The significance of each element is up to your organization’s software release policy.

Note    In Visual Basic 6, <RevisionNumber> appears as the third element and the <BuildNumber> element is not visible. The file version number of Visual Basic 6 executables include all four elements but the <BuildNumber> element is 0 by default.

For example, if you have deployed an extension with file version number 1.0.0.0, to deploy an updated extension, you can change its version number to 1.0.1.0.

To build a package for an updated extension:

1. In Visual Studio or Visual Basic 6, open the project’s properties.
2. In Visual Studio, click the Application tab. The Application options page appears. In Visual Basic 6, click the Make tab. The Make options page appears.
3. In Visual Studio, click the Assembly Information button. The Assembly Information dialog appears. In Visual Basic 6, proceed with the next step.
4. In Visual Studio, change one of the elements of Assembly Version and of File Version. In Visual Basic 6, change one of the elements of Version Number.

Tip    To automatically increment the version number whenever you rebuild an extension, in Visual Studio enter an asterisk (*) for the element that you want to increment. In Visual Basic 6, select the Auto Increment check box.

5. Click OK to save your changes.
6. Build the project.
7. Package a .NET extension library into a .CAB file with the PackageBuilder tool as described in "Packaging a .NET user interface extension" in the Meridian Enterprise .NET API Reference. Package a Visual Basic 6 extension into a .CAB file with the Package and Deployment Wizard as described in Packaging an interface extension .
8. Register the extension in Meridian Enterprise Configurator as described in Registering an interface extension .

The Meridian Enterprise clients will automatically install the updated extension when they next open the vault.

Related information

Packaging an interface extension

"Packaging a .NET user interface extension" in the Meridian Enterprise .NET API Reference.

Registering an interface extension

Windows Installer Guide: Patching and Upgrades
http://msdn.microsoft.com/en-us/library/aa370579(VS.85).aspx

Windows Installer: File Versioning Rules
http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx

.NET Framework Developer's Guide: Assembly Versioning
http://msdn.microsoft.com/en-us/library/51ket42z.aspx