Hi,

You need to add the licenses.islicx in each project that uses ClientUI control. The license should be generated by the tool on the developer machine. The license should be generated based on your current project assemblies.

You also need to regenerate the license if you make a major changes in your project. However, if you are not sure if the changes is major or minor, you can simply build the project and regenerate the license.

Regarding your question, "We have multiple release configurations, do we need to generate lincese for each one? If yes, how should we do it?"

I assume multiple release configuration as multiple projects (please correct me if I am wrong). As I mentioned above,  in your each project that used ClientUI control, you need to add license.islicx.

However, I recommend that you perform the licensing process at the time when your Silverlight application is ready to deploy so you won't have to generate for many times.

When deploying the application, you won't need to install the product in your server.

Regards,

Lili

I've added licenses.islicx to the second project and it worked.

When I was talking about multiple release configurations, I have meant that we have configurations in Visual Studio like Release, Demo Release, Express Release. Each configuration defines some conditional compilation symbols (DEMO, EXPRESS) that can alter what code is considered for compilation (using #if DEMO directive).  It may be possible to need different license strings for different configurations?

Hi,

If you change the configuration that you use, the build will change so you need to re-generate the license everytime you change the configuration.

Regards,

Lili

After numerous tries, we finally solved the problem. I am writing this because hopefully will help somebody else.

 The build machine automatically increase de version of the assemblies. Apparently, the license mechanism uses this. Therefore, although we did not make any changes to our Silverlight projects, the license will be invalid. We made a work around by not increasing anymore the assembly version of the Silverlight projects.

 It is disappointing that there is not any documentation about this and we found this by trial & error. A licensing console utility that could be integrated in the build scripts will be greatly appreciated. We have a lot of builds (release, testing, nightly) & configurations and manual generation is just a loss of time.

Hi,

I'm glad that your problem is solved. Thank you for your feedback and for sharing the result.

Regards,

Lili

I want to say that i don't consider the problem solved, but worked around. There's a difference that for me is important...

Hello,

Thanks for your feedback. Actually, the runtime licensing tool already supports build automation through command line arguments.

You need to supply five parameters to the runtime licensing executable through command line:

• /assembly
• /product
• /version
• /runtimeLicenseKey
• /output

Intersoft.ClientUI.Licensing.v4.exe 
     /assembly="D:\Assembly\Asm1.dll" 
     /product=Intersoft.ClientUI /version=5.0.5000 
     /runtimeLicenseKey=1234-56789-1234 
     /output="D:\Projects\App1\licenses.islicx"

Best,
Jimmy