The following development environments are supported for various
software development tasks that enable you to automate, extend, integrate, and
otherwise customize you STK experience:
- .NET (Visual Basic, C#, etc.) can be used for
all development tasks using AGI technologies. Primary Interop
Assemblies are provided for better interoperability with the .NET
platform. Visual Studio 2015,Visual Studio 2013, and Visual Studio
2012 are supported. For workarounds to known issues, see Visual Studio 2012 Notes.
The STK Engine libraries use single threaded apartment (STA)
components. Therefore, in .NET, make sure that the threads in which
you use the STK Engine components are correctly marked as STA by
using the STAThread attribute or the Thread.ApartmentState property.
- Java can be
used for all development tasks using AGI technologies except
extending STK. Jar files are provided out-of-the-box for the STK
Engine and partial COM automation libraries. Java development can
be done using standard Java development environments such as
Eclipse. Both the SWT and AWT frameworks are supported.
- C++ can be used for all the tasks by directly
importing the proper type libraries.
- Other environments (VBScript, JScript, Perl,
Python, MATLAB, etc.) can also be used to extend and script
AGI provides a variety of ways to use and incorporate our
technologies. Code samples that demonstrate various ways to
automate and extend the STK application or build custom
applications in various development environments (C#, C++, Visual
Basic, Java, MATLAB, Perl, Python, VBScript, JScript) are shipped
A full listing of available samples, their function, and
location in the install are provided in separate sections. Code
samples are organized according to their function in the install.
Use the links below to jump to a particular area of interest.
For the Visual Studio samples, the solution and project files
are in Visual Studio 2015,Visual Studio 2013, and Visual Studio
2012 formats. All file names contain "_VS2015", "_VS2013", or
"_VS2012", indicating the format type.
Visual Studio 2012 Notes
There is the workaround for a known issue with Visual Studio
Assembly References Do Not Update When Project Output is
The problem is the new option introduced with .NET 4.0 that
allows you to embed the interop types into the application
assembly, thus minimizing the size of the assembly that depends on
the interop types. This was done primarily for Microsoft Office
The workaround is:
- Change the framework version to .NET 4.0.
- Click the References folder in the project
- Select all AGI interop assemblies, including stdole.dll
- In the Properties window, set the Embed Interop Types to
- Change the target framework back to .NET
- Refresh the dependencies of the Setup project. The AGI primary
assemblies should show up in the dependencies list.
STK 11.2.1 Programming Interface