The TReK Command .NET API contains the same functions that are in the TReK Command API. Each function is wrapped with a .NET wrapper, which allows its use in a .NET environments.

All functions in the API are thread safe. An overview of the capabilities in the Command .NET API are provided in the (trek::trek_cmd_user_api) section.

Release 3 Compatible Command .NET API Notes
The Release 3 Compatible Command .NET API is provided to allow user applications that integrated TReK 3.x .NET APIs an easy path to upgrade to the latest TReK release. Here are a few of the currently supported functions:

Sending Commands

Updating Commands

Destination Specifics

Currently Unsupported Functions.
Some of the functions from the Release 3 .NET API are not planned to be supported at this time. If you use these functions and need to continue using them in the future, please contact the TReK help desk.

Get_Validation_Event_Name()
Change_Uplink_Packet()
Get_Uplink_Packet_For_Validation()
Send_Validation_Results()
Uplink_TReK_Command()
Update_Destination_Database()

Examples
The following examples are provided to show how to use Command .NET APIs.

Command .NET Example
Uses the Release 3 Compatible API to uplink a command.
Source File:
Command_Example/Program.cs

Additional Dependencies
The TReK Command .NET API is also dependent on the following libraries. See the Libraries main help page for more information.

trek_toolkit_common_api
trek_command_api
trek_cmd_user_api
trek_toolkit_data_api
trek_toolkit_utilities_api
xerces-c_3_1