Runtime License File in WPF

yudi — Mon, 13 Jun 2011 08:21:06 GMT

I have forwarded this to ClientUI development team to be investigated further.
I’ll keep you updated with any news I heard from the team regarding this topic.

Runtime License File in WPF

pavritch — Sat, 11 Jun 2011 03:56:48 GMT

I'm generally familiar with getting the runtime licensing to work for ClientUI WPF projects. However, for this one project I could not get out of evaluation mode no matter what I tried.

I figured I'd start with a new WPF empty shell created using the Intersoft ClientUI5 template and see if I could recreate the problem with nothing more than a single button in the main window. And I did.

I finally came to realize that if I changed the project default namespace to something other than what it was when the project was created, the program always remains in evaluation mode. The same goes for if I change the assembly name. This is true even when re-running the license manager after making such changes just in case there was a dependency.

I then went back to my original "big" program, changed the default namespace to what it was when I initially created the project, created a new runtime license file - and it worked. However, now the namespace isn't what I'd prefer.

Apparently there is some not-so-obvious relationship between the license file, assembly name, default namespace and I'll assume the assembly GUID.

Can you please describe this delicate relationship and/or explain what steps to take when changing the assembly name or default namespace after creating a project.

I never would have thought the original default namespace was so tightly integrated into licensing....did I miss something?

Thank you!

Peter

Intersoft Community - ClientUI - Runtime License File in WPF

Runtime License File in WPF

Runtime License File in WPF