Deploying an STK Engine Application

There are several ways to create an installation package for an STK Engine application. You can:

• Use Visual Studio to Create an Installation Package
• Use InstallShield to Create an Installation Package
• Use the STK Engine Microsoft Software Install (MSI)

The process of deploying an application will depend on whether the application will be installed on a system where STK is already installed or a system that does not have STK installed. The items below outline the requirements for each option. Each set of instructions above includes instructions for creating an install for applications that may or may not be deployed on systems that already have STK installed.

• Install on a system where STK is already installed. If STK is running on your system, you only need to install the STK Engine application files.
• Install on a system that does not have STK installed using the STK Engine MSI. Use this option if you have a limited distribution of the application on systems, other than your system, that do not have STK.
• Install using the STK Engine Merge Modules. Use this option when the embedded STK Engine functionality is widely distributed with your application. Merge modules are provided to support the creation of your own custom installation package. The following merge modules are available:

• 64-bit binaries and base data set

  • C:\Program Files (x86)\Common Files\Merge Modules\STK_Engine_Binaries_11_X64.msm 64-bit binaries
  • C:\Program Files (x86)\Common Files\Merge Modules\STK_Engine_CommonData_11_X64.msm

  32-bit binaries and base data set

  • C:\Program Files (x86)\Common Files\Merge Modules\STK_Engine_Binaries_11.msm
  • C:\Program Files (x86)\Common Files\Merge Modules\STK_Engine_CommonData_11.msm

Note: You can include the AGI License Server when deploying an STK Engine application.

STK Engine Application Installation Requirements

When creating an installation package for an STK Engine Application, it's important for the STK Engine Application's installer to adhere to the following algorithm:

IF STK exists on the computer where the STK Engine Application will be installed THEN

To detect the presence of an STK installation, the installer should look for the existence of one the following registry keys:

For STK 8: HKEY_LOCAL_MACHINE\Software\AGI\STK\8.0

For STK 9: HKEY_LOCAL_MACHINE\Software\AGI\STK\9.0

    Check the version of STK that's installed 

To obtain the specific version of an STK installation, the installer can examine the DisplayVersion string value contained within the following registry keys:

For STK 8: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{4D1348FA-48F8-417D-BA50-5B668ADB96CF}

For STK 9: HKEY_LOCAL_MACHINE\Software\AGI\STK\9.0

    IF the installed STK version is greater than or equal to the version used to build the STK Engine Application THEN
        Do NOT install the STK merge modules
        Install the STK Engine Application
    ELSE IF the installed STK version is less than the version used to build the STK Engine Application THEN
        Notify the user to upgrade STK to the same major version that was used to build the STK Engine Application
    ENDIF
ELSE IF STK does not exist THEN
    Install the STK merge modules
    Install the STK Engine Application
ENDIF

STK Programming Interface 11.0.1