API Implementation
- Meaning of “Implementation with API”
- Recommended Steps for Protecting Applications with API
- Smarx®OS as the Basis for the CRYPTO-BOX Integration
- Smarx®OS API Subsets
- Using the Smarx®OS API under Different Environments
- Static Libraries (C/C++, Delphi)
- Dynamic Libraries (DLL)
- .NET
- COM/ActiveX
- Library and Sample Code for Your Environment
- Library and Samplecode from the Protection Kit
.NET
MARX provides .NET developers with an object oriented, component-based approach that simplifies the integration of software protection and licensing for .NET applications.
INFO
| If you are working with Visual Studio 2013 and higher, you can use our Smarx API, which is based on CBIOS4NET. For a description of the Smarx API, see Chapter 11 of the Smarx Compendium. |
If an older environment (under Visual Studio 2013) is used or custom protection and licensing options are required, consider CBIOS+DO API instead of Smarx API.
CBIOS and DO API are available to .NET developers in Smarx4Net or CBIOS4NET. For more information, see the .NET interfaces for developers table, below.
Both interfaces combine all Smarx programming interfaces under one roof for .NET platform:
The following CRYPTO-BOX models are supported:
- CRYPTO-BOX® SC (CBU SC),
- CRYPTO-BOX® XS (CBU),
- CRYPTO-BOX® Versa (CBU).
IMPORTANT NOTE:
The CBIOS4NET Developer's Guide contains an introduction to CBIOS4NET and a detailed description of its classes.
* Smarx4Net requires CBIOS Network Server for local mode
** Included to MSI/MSM