Robust Packaging and Deployment.

  • UV
  • UD
  • D3
  • QM

Deploy with Confidence

Whether distributing software to your clients, preparing quality releases for testing and acceptance or promoting changes from development to live, a fully automated and robust deployment method is an essential part of any infrastructure.

Without a guaranteed, predictable and hands-free installation process, all your testing and release planning count for nothing when a mistake is made or a step missed in a manual installation process.

I depend on mvInstaller as a rock solid way to test and deliver my own products.



Choose your Installer

mvInstaller features native Windows, Microsoft .NET and server side installers to give you and your clients the flexibility to choose the most convenient installation option.

mvInstaller packages can also be run through Jenkins using the mvTest CI Builder as part of your managed integration testing or  continuous deployment pipeline.

What is easier and more fool-proof - giving someone a long list of instructions, manually copying and compiling items or providing a tested package they can install with a single command?


mvInstaller Clients

Designed for MultiValue

MultiValue applications can be complex, and so setting up or updating an application can demand much more than simply copying items around.

mvInstaller has all the features necessary for deploying real world MultiValue applications including version sensitive operations using your choice of versioning or the built-in mvStamp support, and safe backouts that can remove setups whilst preserving items that may have changed in the intervening period such as counters.


  • Create files (all types) and indices.
  • Install dictionary and data items.
  • Install, compile and catalog programs.
  • Install object code and binary data.
  • Update fields and values in data items.
  • Run commands during build and setup.
  • Call handler subroutines.
  • Safely back out your changes.

Integrated with Release Procedures

mvInstaller packages are binary, compressed files of data and actions that are easy to generate, test and archive, and provide a perfect transfer mechanism for sites that need to separate development from installation for compliance and audit purposes.

Packages are defined using an easy-to-learn scripting language that can be hand crafted, automatically generated from your release procedures or built using the point-and-click WIndows based GUI client.

Combine this with the command line based package builder to generate your setups directly from your cutting PROCs and paragraphs.

You can even include select commands within the package definitions to pick up items for inclusion based on any criteria you need to identify candidates for deployment.




Customize your Setups

Packages are organized into sections and groups, which may be optional or mandatory, allowing your clients to select features on installation.

But beyond that, handler routines - special subroutines included in your setups - can be added that control which sections are run, letting you create fully customized setups, check for licences, provide additional features or tailor the installation to different environments.

Handler routines are called on backouts also, allowing you to sensitively rewind such entries as parameter items.


Version sensitive installations are natively performed using the free mvStamp version stamps for your code and assets but you can also supply your own routines to identify version differences and numbering.

You can similarly override the regular compile and catalog commands with your own custom routines.