All ScriptX.Add‑on functionality can be fully tested on a development machine with a FREE evaluation license, and basic ScriptX functionality can be tested and deployed on your intranet or the public internet without a license.

This allows you to fully evaluate and test ScriptX.Add‑on before purchasing a publishing license.

We also recommend taking a look at the guide to deployment, our samples and the Technical Reference in our Knowledge Bank.

The appropriate version of ScriptX to use depends on your target client platform:

  • If all your end users are running Internet Explorer 11 you should use ScriptX 8 (latest version is 8.1.0.2)
  • If your application also needs to support older versions of Internet Explorer from 6 to 11 use ScriptX 7 (latest version is 7.8.0.2)

Step 1: Evaluate ScriptX.Add‑on on a development machine

ScriptX.Add‑on can be fully tested with a FREE evaluation license on content served from the local file system (file://, My Computer Security Zone only) or local website (http://localhost/).

Step 2: Deploy ScriptX.Add‑on for FREE

The basic features of ScriptX.Add‑on are available for no charge, for example, the ability to specify print headers and footers, margins and orientation. You are free to deploy the binaries provided to your servers on your intranet or the public internet.

Step 3: Deploy ScriptX.Add‑on with a publishing license

A paid-for publishing license is provided to registered customers. This unlocks the full power of ScriptX.Add‑on from your own root URLs. Your publishing license will work with every existing and future version of ScriptX.Add‑on, and by request can be extended to include ScriptX.Services. It does not have to be updated when the ScriptX software is updated. All publishing licenses are renewable and valid for one or more years.

Step 1: Evaluate ScriptX.Add-on on a development machine

ScriptX.Add‑on installation is developed using Internet Component Download file‑based installers where the installer is provided as a .cab file. Installation via the smsx.cab file is recommended where online delivery and deployment via Internet Explorer is required - it has the advantage of being simple to implement. The smsx.cab installer is a convenient wrapper on ScriptX.msi.

Please remember when using the evaluation license that ScriptX.Add‑on can only be tested on content served from (specifically and ONLY) the local file system (file://, My Computer Security Zone only) or local website (http://localhost/).

The instructions below describe ScriptX‑enabling a page for deployment of ScriptX.Add‑on. This then makes ScriptX.Add‑on available on your page for scripting to provide a controlled printing experience for your users. Complete ScriptX.Add‑on documentation is available in the Knowledge Bank. A comprehensive set of samples is available here - feel free to use ‘View Source’ and copy and paste any code you want.

Browser-based deployment

You will need:

  • or
  • the evaluation publishing license (automatically downloaded from the MeadCo servers)

smsx.cab should be copied to a suitable location on your web server(s), then include these objects on your pages:

where [your-path] is a placeholder for the location of smsx.cab on your own servers.

The <object> code shown above should appear on ALL your ScriptX‑enabled pages, including those dynamically created on the server via ASP Classic, ASP.NET, PHP etc. You cannot use CreateObject or new ActiveXObject to call ScriptX client‑side.

When scripting, you should call ScriptX in all cases by the ID of the ScriptX object on the page - in the above example ‘factory’.

The {c4db5d29-be52-46b9-9ddf-46a167170f81} value of the GUID parameter used above identifies the MeadCo evaluation license that authors may use to experiment with Advanced printing capabilities. The license validates local file system (file://), My Computer Security Zone only) and local website (http://localhost/) content only for evaluation purposes on a single development computer.

The evaluation license does not validate and will not work with any other URL. Registered customers are issued with their own unique license identifier and a digitally signed sxlic.mlf file.

Administrator pre-install

Alternatively you may wish to pre-install ScriptX.Add‑on over an intranet, in which case you will need:

  • or
  • the evaluation publishing license (automatically downloaded from the MeadCo servers)

Run the installer file ScriptX.msi (you will need to be logged in as an Administrator) as an alternative to having the add‑on download automatically the first time you as a user hits a ScriptX‑enabled page. Once installed on your machine, ScriptX is made available on your pages as described in Browser‑based deployment. When installed in this way the codebase parameter should be removed.

Step 2: Deploy ScriptX.Add‑on for FREE

The basic features of ScriptX.Add‑on are available for no charge. This includes for example the ability to specify print headers and footers, margins and orientation. You are free to deploy the binaries provided to your servers on your intranet or the public internet.

Browser-based deployment

You will need:

  • or

smsx.cab should be copied to a suitable location on your web server(s), then include this object on your pages:

or, if you wish to make use of MeadCo's version of the IE7 ‘scale to fit’ print template, independent of your user's version of Internet Explorer, do this:

where [your-path] is a placeholder for the location of smsx.cab on your own servers.

The <object> code shown above should appear on ALL your ScriptX‑enabled pages, including those dynamically created on the server via ASP Classic, ASP.NET, PHP etc. You cannot use CreateObject or new ActiveXObject to call ScriptX client‑side.

When scripting, you should call ScriptX in all cases by the ID of the ScriptX object on the page - in the above example ‘factory’.

Administrator pre-install

Alternatively you may wish to pre-install ScriptX.Add‑on over an intranet, in which case you will need:

  • or

A local administrator should run ScriptX.msi on each client machine on your intranet as an alternative to having the add‑on download automatically the first time a user hits a ScriptX‑enabled page. This approach will be more suitable if your users don't have the privileges to run installers themselves.

Once deployed in this manner, ScriptX is made available on your pages as described in Browser‑based deployment. If you know that ScriptX has already been deployed the codebase parameter should be removed.

Step 3: Deploy ScriptX.Add-on with a publishing license

If you are a registered ScriptX.Add-on customer you can use the download links below for deployment, however you will need to refer to the installation instructions that you received with your publishing license.

Browser-based deployment

You will need:

  • or
  • your publishing license file sxlic.mlf, as described in your email notification of license availability

This file should be copied to a suitable location on your web server(s), then include these objects on your pages:

where [your-path] is a placeholder for the location of smsx.cab on your own servers, and [YOUR_LICENSE_GUID] and [your license rev] are details that will have been provided to you in your email notification of license availability.

The <object> code shown above should appear on ALL your ScriptX‑enabled pages, including those dynamically created on the server via ASP Classic, ASP.NET, PHP etc. You cannot use CreateObject or new ActiveXObject to call ScriptX client‑side.

When scripting, you should call ScriptX in all cases by the ID of the ScriptX object on the page - in the above example ‘factory’.

Administrator pre-install

Alternatively you may wish to pre-install ScriptX.Add‑on over an intranet, in which case you will need:

  • or
  • your publishing license file sxlic.mlf, as described in your email notification of license availability

A local administrator should run ScriptX.msi on each client machine on your intranet as an alternative to having the add‑on download automatically the first time a user hits a ScriptX‑enabled page. This approach will be more suitable if your users don't have the privileges to run installers themselves.

Once deployed in this manner, ScriptX is made available on your pages as described in Browser‑based deployment. If you know that ScriptX has already been deployed the codebase parameter can be removed.

Not using Internet Explorer?

NEW ScriptX.Services has been developed by popular demand to bring consistent print formatting and appearance to Firefox, Chrome, Edge and Safari.

Show me ScriptX.Services