Intersoft Community - ClientUI - License problems

License problems

jimmyps — Tue, 28 Jun 2011 05:44:43 GMT

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

Usage example:

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"

Note that you should already have the licenses.islicx in your Visual Studio project which build action is set to Embedded Resource. This allows the runtime licensing to simply override the license file just before compilation.

Your build steps should be: compile, licensing, rebuild.

I hope this helps.

Best,
Jimmy

License problems

catalin — Tue, 28 Jun 2011 04:39:32 GMT

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

License problems

lili — Tue, 21 Jun 2011 06:23:27 GMT

Hi,

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

Regards,

Lili

License problems

catalin — Mon, 20 Jun 2011 04:01:10 GMT

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.

License problems

lili — Wed, 15 Jun 2011 03:45:04 GMT

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

License problems

catalin — Fri, 10 Jun 2011 04:50:01 GMT

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?

License problems

lili — Tue, 07 Jun 2011 22:41:59 GMT

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

License problems

catalin — Mon, 06 Jun 2011 01:34:34 GMT

Hello,

We have problems setting the run-time license for our Silverlight application - the unlicensed version message appears. Our Silverlight application consists of two Silverlight projects: Dashboard and MVVMFramework. The MVVMFramework is a library project, containing common classes and custom controls (some of them use Intersoft ClientUI controls). The Dashboard project is the main Silverlight application and uses ClientUI controls too.

To include the license we followed the steps from the documentation:

- Build Dashboard & MVVMFramework on a developer machine (Debug configuration)

- Run the License tool and select Dashboard.dll

- Include in Dashboard project the file licenses.islicx with the content from the tool. Set it as Embedded Resource

The final build is done by our build server. We have multiple release configurations for our product. On the build server we installed ClientUI 4.0 too.

The problem is that the unlicensed version message appears when our product is deployed on a server and is accessed from a client browser.

1. Do we need to include licenses.islicx in MVVMFramework project too?

2. Where the license should be generated by the tool (on a developer machine or on the build server)?

3. The license should be generated for every release build?

4. If we make modifications to the Silverlight projects (adding new controls, pages) do we need to generate a new license?

5. We have multiple release configurations, do we need to generate license for each one? If yes, how should we do it?

6. Do we need ClientUI 4.0 installed on the build server and registered? Or we can just copy the needed Intersoft dlls?