This topic provides information about the licensing instruction to be applied to the application before it is deployed to live server or distributed to clients.
ClientUI requires runtime application licensing to protect your intellectual property and to ensure your applications to be protected from modification after deployed or distributed to your clients. Note that the runtime licensing is not identical with the license key used for development. You can obtain the runtime license key from Intersoft Developer Network.
 |
With a valid developer license, you are entitled to get a runtime key which you can use to license your application before deployment. |
Locating Intersoft Runtime Application Licensing
You can locate the application from the program group according to your application platform. For example, to license a Silverlight 4 application, locate the Runtime Application Licensing for Silverlight 4 from the following program grou path: Start Menu, All Programs, Intersoft WebUI Studio 2010 R1, WebUI Studio for Silverlight 4.
The following illustration shows the location of the Runtime Application Licensing for Silverlight 4 in Windows 7 program group.
Using Runtime Application Licensing
To license your application that uses ClientUI, you need to obtain your runtime license key if you haven't done so. Please login to Intersoft Developer Network and locate the ClientUI product under My Components module, then click the Register button to get the runtime license key.
 |
Please keep your runtime license key safe and treat it as confidential as the design license key to avoid licensing problem in your distributed application. For more information, see ClientUI License Agreement. |
The following illustration shows the runtime application licensing program used to generate the license identifier for each ClientUI-powered application.
Select the main assembly of the application to be licensed and then click the Generate button to get the license ID to be placed in your application. Please refer to the following illustration.
|
You only need to generate the ClientUI application license on the main assembly that represents your application. In a Silverlight application, the main assembly refers to the type associated to the root visual. In a WPF application, the main assembly refers to the type associated to the startup window, or the type constructed in the Main method of the application. |
Applying the Generated License to Silverlight Project
There are two methods to apply the generated license to a Silverlight project.
- The first method is by adding a license file named licenses.islicx to the root folder of your Silverlight project, and paste the license ID generated by the program mentioned above. It’s important to set the file’s ContentType to Embedded Resource to properly embed the license file in your Silverlight assembly.
- If adding a new file to the root folder of your project is not feasible, you can use the second method to license your application which is done through the ClientUILicenseInfo assembly-level attribute definition. Normally, you define the attribute in the AssemblyInfo.cs file of your project, or alternatively you can define it in just any compiled files in your project.
The following example shows how to license ClientUI in your application through the provided attribute.
[assembly: ClientUILicenseInfo("<Licenses><Product Name="Intersoft.ClientUI" Version="3.0.5000" Stamp="[Insert the generated license]" /></Licenses>")]
|
If you’re using ClientUI Application Framework to load the content from an external XAP, the assembly of that external XAP is required to be licensed as well. |