The implementation with API gives you more flexibility.
Please read our Implementation with API White Paper. It gives you a good introduction on how to start. Be sure to also refer to the samples located within the PPK as well for examples of each.
Currently Windows, Linux, Mac OS X, iOS (network mode only) and Android are supported.
A detailed overview of supported compilers can be found in the Implementation with API White Paper, chapter 4.
Nothing can be completely 100% secure, but there are multiple precautions you can take to make your program more protected thus making it more difficult for crackers to breach your applications protection.
More tips and details can be found in the Smarx Compendium, chapter 17.
This is not necessary. Under Windows you can use the Smarx Application Framework (part of the CRYPTO-BOX Protection Kit) to program the CRYPTO-BOX units. See Smarx Compendium, chapter 4.5 for more details.
Furthermore with SmrxProg there is a command line tool available (for Windows, Linux and Mac OS X) which takes care of CRYPTO-BOX formatting. It provides a high grade of automation, because the formatting process can be controlled within other applications or script-files. Please refer to the Smarx Compendium, chapter 7 for more details.
Many environments allow to incorporate C routines. Another possibility under Windows is using COM technology or the dynamic library cbios_dll.dll provided in the Smarx OS Protection Kit – see Smarx Compendium, chapter 10.12 for more details.
If you look for support of older environments of development environments: we still support a lot of older compilers, such as old Visual Studio or Delphi versions, as well as legacy environments, eg. older Windows or Linux versions, real-time OS or even DOS (via the CRYPTO-BOX Serial).
Please contact us to discuss further details: We will find a solution in almost all cases.
Because of the nature of .NET, unprotected .NET assemblies can be decompiled easily by advanced programmers and crackers which makes it more easy to detect and remove the protection routines from your application. Therefore it is necessary to protect the code.
Here are some hints:
Furthermore, we are offering consulting and implementation support on request - please contact us to discuss your requirements.