The ClientProtector is a COM component DLL. To link to the ClientProtectorCOM.dll, your application installer must distribute and register the DLL along with your application and license and any other supporting files your license may need. If you are using IronWrap, you do not have to directly interface with this component if you don't need to, everything will be managed for you. However, even if you do use IronWrap you will have the option of interfacing with the component for a fully integrated solution. The first step to using the ClientProtector in your application is always to create an instance of the component in memory. Your application must do this immediately upon starting and before trying to use it - just like any other COM component. Note that when you choose IronWrap, you interface with the COM component just like you would if the file is deployed and registered on the target system. The IronWrap system virtualizes this access for your game. Therefore, you do not need to register the COM server on the users machine - or even deploy the DLL! When you compile your license, the GameShield License Manager writes sample code for you in three different languages (C++, VB and Delphi) that allows you to get a quick start integrating the ClientProtector into your application. In the simplest of cases the code required to enforce your license using the ClientProtector in your application is just a few lines. All the logic for enforcing a license is already inside the ClientProtector. Naturally, the more complex you design your license to be, the more code will be required between your software and the ClientProtector. A high-level view of the steps for integrating the ClientProtector into your software follows:
That's all there is to it. |
||||
