Distributing Spinnaker Applications

Please see Teledyne's End User License Agreement for the Spinnaker SDK.

Note: As of version 4.0 Spinnaker no longer supports Myricom Cards MVA or Windows 7.

There are two methods for distributing applications built with the Spinnaker SDK:

1. Automatic Silent Install—this is the recommended method as it ensures all necessary components are included
2. Custom Distribution of Files and Runtimes—this method allows the flexibility of only including the files you need but requires more expertise. See also Installing Spinnaker from the Command Line.

Automatic Silent Install

This is the recommended method. It is available in Spinnaker 4.x or newer.

Launch a command line silent install option using the Spinnaker .exe installer file.

Bolded features listed in the table will automatically select additional features to install:

Example Command Line Options

For minimal runtime installation:

For silent uninstallation:

Custom Distribution of Files and Runtimes

This method allows the flexibility of only including the files you need but requires more expertise. See also Installing Spinnaker from the Command Line.

When distributing applications built with the Spinnaker SDK, certain files must be included with the package:

• Spinnaker dll and configuration files (see List of Spinnaker DLL and configuration files table below)
• Microsoft Visual Studio and .NET runtimes (The version of Visual Studio and .NET runtimes depend on which Spinnaker version is installed.)

Spinnaker dll and Configuration Files

The files that must be included with the distribution depend on the interface used to program the application.

The list of Spinnaker DLL and configurations files (table below) indicates the files required for inclusion in application distributions, depending on the programming interface. The files are installed by default in the bin or bin64 folder of the Spinnaker installation directory.

The dll files are provided for three versions of Visual Studio:

If using:

SpinUpdateConsole (C++ program that is used for updating the device firmware)

• This application only requires the SpinUpdate_*.dll

SpinSwitchConsole (C++ program that is used for installing the device driver)

• This application only requires the SpinSwitchClassLibrary_*.dll

List of Spinnaker DLL and configuration files

Microsoft Visual Studio and .NET Runtimes

Regardless of the Visual Studio version used to compile the end application, user computers must include the Visual Studio runtimes used when the dll files were compiled at Teledyne. Our build servers are updated with Microsoft updates.

Note: The runtimes to install must match what was used to compile the dll files. For example, if using a 32-bit application and the 32-bit Spinnaker dll files on a 64-bit operating system, the user must have the 32-bit Visual Studio runtimes. If using the 64-bit Spinnaker dll files then the 64-bit Visual Studio runtimes are required.

Runtimes can be distributed in three ways:

1. Install the Spinnaker installer to include the correct runtimes. This is the preferred method. Using the msi installer and parameters, the Spinnaker installer runs quietly with no prompts, and is set to install the Runtime Libraries only. The most common reason for not using this method is that the complete Spinnaker installer needs to be included in the package and it is a significant size.
2. Install the redistributable package found on the Microsoft website. End users can be pointed to the Microsoft link, or the package can be included as part of an installer (with no prompts).
3. Install the runtimes separately using merge modules in the installer. This allows the distributor to include only the runtimes required by the Spinnaker dll files. 

Note: If using method 2 or 3, include the runtime version for the Visual Studio release as listed in the table below. 

List of runtime and .NET versions

The runtime modules required by Spinnaker are:

For VS2010

• • Microsoft_VC100_ATL
  • Microsoft_VC100_CRT
  • Microsoft_VC100_MFC
  • Microsoft_VC100_MFCLOC
  • Microsoft_VC100_OpenMP
  • policy_8_0_Microsoft_VC100_ATL
  • policy_8_0_Microsoft_VC100_CRT
  • policy_8_0_Microsoft_VC100_MFC
  • policy_8_0_Microsoft_VC100_MFCLOC
  • policy_8_0_Microsoft_VC100_OpenMP

For VS2013

• • Microsoft_VC120_AT
  • Microsoft_VC120_CRT
  • Microsoft_VC120_MFC
  • Microsoft_VC120_MFCLOC
  • Microsoft_VC120_OpenMP
  • policy_8_0_Microsoft_VC120_ATL
  • policy_8_0_Microsoft_VC120_CRT
  • policy_8_0_Microsoft_VC120_MFC
  • policy_8_0_Microsoft_VC120_MFCLOC
  • policy_8_0_Microsoft_VC120_OpenMP

For VS2015

• • In VS2015, it is no longer sufficient to provide just the merge modules as the universal crt libraries are not packaged with them. Users must install the vcredist.exe provided by Microsoft. 

Note: A subset of the library may only require a subset of the merge modules. We publish the full list due to the large number of potential combinations, and the relatively small footprint of the modules.