Catalyst Knowledge Base

Creating SocketTools Runtime License Key

Document ID: 100223
Products: SocketTools, All Editions 6.0, All Platforms
Last Reviewed: December 14, 2009

Summary

To redistribute an application created using the SocketTools components or dynamic link libraries, it is required that you call the initialization method or function with a valid runtime license key. This is discussed in several places in the help, including the Licensing Information section, the Initialization section in the Developer's Guide and the initialization functions and/or methods in the Technical Reference. It should be noted that your serial number and the runtime license key are not the same, and cannot be used interchangeably.

For applications written in C/C++, the header file csrtkey6.h contains your runtime license key. For applications written in Visual Basic, the module file name is csrtkey6.bas. These files can be located in the Include folder where SocketTools was installed. Note that for other programming languages, you should be able to use the string value as defined in the Visual Basic module, which is a text file.

Normally, this runtime key constant is defined when the product is installed with a valid serial number. However, in some cases the key may not be defined if the product is installed as an evaluation and then a license is purchased. If the key value is defined as an empty string or a NULL value, you will need to manually create the header or module file.

Note that it is not typically necessary to explicitly initialize a SocketTools ActiveX control with a runtime license key unless you are creating an instance of the control dynamically using CreateObject or using it in a managed .NET application using COM Interop.

More Information

To manually create a runtime license key header or module file, run the License Manager utility in the SocketTools program folder. Once you have started the License Manager, first select which edition of SocketTools you're creating the runtime license key for. This is done through the menu option License | Product and selecting the product that you wish to create the runtime license key for. Note that the correct edition may already be checked.

Next, select the menu option License | Validate, which should display a dialog which displays the current version, your serial number and a license expiration of "Never". If no serial number is displayed or the license has an expiration date, then this means that an evaluation license has been installed for this product. You will need to install the product with a serial number in order to create a runtime license key.

The last step is to select the License | Header File menu option. A Save File dialog will be displayed, which will allow you to select where the header or module file will be created. Use the Save as Type dropdown list to select the programming language that you are using. If your language is not listed, then select Text File and specify a filename with a .txt extension. This will create a plain text file which contains the runtime license key. The current version of the License Manager utility also has a menu option named License | Runtime Key will will display the runtime license key and allow you to copy it to the clipboard.

You can now either include this file in your project, or cut and paste the key value into your application. Remember that this key is specific to your license and should not be shared with anyone outside of your organization.

Feedback
Please tell us how useful this article was in answering your question:
Not Answered Partial Answer Completely Answered

Let us know if you have any feedback on how this article could be improved,
or suggestions for additional Knowledge Base articles:
Email Address:
If you would like a response to your feedback, please provide your email address