SDKs

The “LowLevel” API described under Extension Services is the basis of every SST component connection. The SDKs also use exactly this interface.

In principle, the development of an SST module “bypassing the SDKs” would also be possible with this information, but a whole series of things would have to be implemented independently.

When using the SDKs, on the other hand, one uses their abstractions. They each contain a set of classes and already implemented components, with the help of which the goal can be reached much faster.

When using the SDKs, the development of an SST module is thus essentially limited to the definition of the object model and the implementation of the communication - the latter also supported in many ways by the SDKs.

C++ - SDK

The C++ SDK consists of a number of libraries as well as a SampleSST, which demonstrates the basic usage by means of the exemplary implementation of a simple SST.

The libraries and functionalities contained in the SDK are also used identically by the WinGuard Core, which is also mostly written in C++.

The use of the C++ SDK is particularly recommended if other external SDKs that are needed are written in C/C++ or have a C/C++ binding.

A detailed description of structure, classes and usage can be found in the separate C++ SDK Documentation.

.NET - SDK

The .NET SDK, written in C#, also consists of a number of components and a SampleSST that demonstrates its basic use with a simple SST implementation.

Most developers will choose the .NET SDK because of the easier pogramming languages and diverse capabilities.

A detailed description of structure, components and usage can be found in the independent .NET SDK Documentation.