Hi Andre,

Do you want to license your clientui in development or deployment server? The above link used for deployment, if you want to license it in the development machine, you just need to use license manager that located in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Intersoft WebUI Studio 2010 R2\License Manager.exe.

For more information on how to use License Manager, you can check the following link:

http://www.intersoftpt.com/Support/Featured/Tutorial/WebUIStudio/Use-License-Manager-to-register-or-remove-Intersoft-products-licenses/

Hope this helps.

Best Regards,

Gordon Tumewu

Hello Yes this is for the development computer.

I have all my keys registered.  The problem is when i click "Play" on Visual studio I get a messeage saying this is  evaluation Version.  I have added licenses.islicx to the root and made it embedded, but I do not know where to point "C:\Program Files (x86)\Intersoft Solutions\ClientUI 4\WPF\LicenseManager\Intersoft.ClientUI.Licensing.v4.exe".  It's asking for a "selecta  silverlight/Wpf applation assembly"  In silverllight I point to the applicationname.DLL, in wpf I pointed it to the .exe and i get an error.

So the question is, on a wpf application what is the assembly?  Since the application is a single form with no .DLL's other then Microsoft's and Intersofts, what is the path to point to?

Attached is the application, please tell me how to License this application.

thanks

Andre

Hello Andre,

Yes, you can select a WPF executable file by choosing it from the file type dropdown in the Select File dialog box.

See the illustration below.

Also, do you create the WPF application from Intersoft's WPF templates?

Hope this helps,
Jimmy

HI,  I did look for the WPF template that looked like the silverlight one's but didn't find them so I created this one from scrach.  I do see 2 templates, next time i'll try them.

as for selecting the .exe, I did try the .exe but i get an error message.

See attached.

Should i start over and use the Intersoft template?

Hi Andre,

The default template for WPF is missing the [assembly: Guid( ... )] attribute in the AssemblyInfo.cs, which is required by the ClientUI runtime licensing. We added this attribute by default in both our SL & WPF templates to ensure the licensing to work properly.

You can simply add that attribute (ensure you put in a unique GUID) to your existing application, recompile and re-run the runtime licensing.

Also, it's recommended that you fill-in the basic properties in the AssemblyInfo.cs to ensure the identity of the application.

Hope this helps,
Jimmy

Thank you, that worked