Deploying with your own installer – Pitney Bowes MapXtreme User Manual
Page 53
Chapter 2: Getting Started
Deploying Your Application
MapXtreme v7.1
53
Developer Guide
3. Follow the prompts to proceed with the installation.
4. Deploy your Windows or Web application as you wish (for example, create a deployment project
in Visual Studio and add your application).
5. Install your runtime license file in the path \\Common Files\MapInfo\MapXtreme\7.x.x under
Program FIles or Program Files(x86), depending on whether you are installing the 64-biti or 32-
bit runtime.
If you wish to run the runtime installer from a command line, follow these instructions. The
executable is located in the [CD root]:\Install\InstallRuntime folder on the product media.
•
To run the runtime installer with minimal UI, execute the runtime installer like this:
MXTRunNCP.exe /v"/qb"
•
To run the runtime installer silently, execute the runtime installer like this:
MXTRunNCP.exe /v"/qn"
If you are using a software copy protected version of MapXtreme, the runtime executable is called
MXTRunSCP.exe.
Deploying With Your Own Installer
Create your own installer using Windows Installer technology (MSI) and include the MapXtreme
merge modules. A merge module (MSM file) is a single package that contains all files, resources,
registry entries, and setup logic necessary to install a component. Merge modules cannot be
installed alone; they must be assimilated into an MSI file. Use this strategy if you want to fine-tune
exactly which components are installed, or if you want to create your own MSI-based installer.
One disadvantage of using the MSMs is that you will have to create your own patch or updated
installer if Pitney Bowes Software provides updates to this product.
An advantage of using the MSMs is that you control which components get installed and reference
counts are maintained automatically. Assemblies of a particular version will be copied into the Global
Assembly Cache (GAC) only once, and reference counts will be maintained for each application
using those assemblies. If one application is subsequently removed, the reference count (which then
decreases by one) will preserve the assemblies in the GAC. When the last application using those
assemblies is removed, then the assemblies themselves will be removed.
Several developer tools are available to help you create an MSI installer. InstallShield Developer
(Acresso Software Corporation) and Visual Studio (Microsoft) are examples. See the Windows
Installer topic in the Microsof