Engine Plugins: Migrating to a new STK version
How to migrate a UI Plugin to STK 12.3
Migration of most UI plugins to a new install of STK requires recompilation and re-registration with STK and the Windows registry before its use. Here is an example UI manifest.
<AGIRegistry>
<CategoryRegistry>
<Category Name="UiPlugins">
<UiPlugin ProgID="..." DisplayName="...">
<LicenseSet Strict="True" Group="STK">STKProfessional,COV</LicenseSet>
<VersionInfo>...</VersionInfo>
</UiPlugin>
</Category>
</CategoryRegistry>
</AGIRegistry>
The manifest above needs to be updated to reference the new STK 12.3 license increments:
<AGIRegistry>
<CategoryRegistry>
<Category Name="UiPlugins">
<UiPlugin ProgID="..." DisplayName="...">
<LicenseSet Strict="True" Group="STK">stk_mission_level1</LicenseSet>
<VersionInfo>...</VersionInfo>
</UiPlugin>
</Category>
</CategoryRegistry>
</AGIRegistry>
The table below describes the license increments to use in the manifest to update the product name.
| Product Name | License Increments | Count |
|---|---|---|
| Ansys STK Pro | stk_mission_level1 | 1 |
| Ansys STK Premium (Air) | stk_mission_level1 stk_mission_level2 stk_mission_air |
1 1 1 |
| Ansys STK Premium (Space) |
stk_mission_level1 stk_mission_level2 stk_mission_space |
1 1 1 |
| Ansys STK Enterprise |
stk_mission_level1 stk_mission_level2 stk_mission_space stk_mission_air |
1 1 1 1 1 |
| Ansys Orbit Determination Tool Kit |
odtk_level1 odtk_level2 |
1 1 |
| Ansys ODSSA | odtk_maneuver | 1 |
| Ansys STK SOLIS | stk_solis | 1 |
| Ansys STK Scheduler | stk_scheduler | 1 |
| Ansys STK Missile Tool Kit | stk_missiles | 1 |
| Ansys Moxie | moxie_sysml | 1 |
| Ansys STK Geospatial Content Server | stk_geoserver | 1 |
| Ansys STK Geospatial Data | stk_geodata | 1 |
How to Migrate a UI Plugin to STK 11
Migration of most UI plugins to a new install of STK requires recompilation and re-registration with STK and the windows registry before its use.
Plugins that are built with a compiler, such as C++ or .NET plugins, cannot be used with multiple versions of STK at a time. They must be recompiled/registered for each version of STK in which they are to be used. The library references within the compilable plugin project must be updated to use the libraries from the STK installation from which they are to be used.
Plugin ProgIDs and GUIDs should also be updated to allow for side-by-side operations across different STK versions.
Refer to Visual Studio .NET documentation for further details on the Visual Studio .NET project and source code details which are beyond the scope of the migration documentation.