Initializing help system before first use

Upgrading from Xpress Insight 4.0 or Earlier

Mosel models compiled with Xpress Insight 2 (Xpress 7.7) or earlier will not work correctly after upgrading to Xpress Insight 4.1 or later.

If you have Mosel models that have not been recently compiled, rebuild them against the latest installation of Xpress/Xpress Insight to resolve any issues.

The mminsight package must now be used at the top of the model, before using any other packages. If this is not the case, you may see an error message when creating the project referring to incomplete entity definitions.

Compiling your model with the -s (strip private symbols) option may result in some entities not being available in Xpress Insight. If this occurs, ensure that the relevant entities are declared within a public declarations block.

Covered Topics
  • VDL 2.0
    For pure VDL views, i.e. not using a custom runner, the only change that should be necessary is to change the VDL version number in each page.
  • JavaScript API 2.0 and Later
    When upgrading a custom VDL runner or a JavaScript API view from version 1.4 or earlier to version 2.0 or later you need to take the several factors into account.
  • Migrating to Bootstrap 3
    JavaScript API 2.0 and later introduce Bootstrap 3 as the framework for HTML layout and styling.
  • Loading the JavaScript API
    Custom HTML views developed against JavaScript API 1.2 or earlier used the RequireJS module system to import the JavaScript API into each view.
  • New Companion File Format
    The format of the companion file has changed since release 3.1 of Xpress Insight.
Parent Topic Upgrade Guide