Intersoft Community - ClientUI - Microsoft Lightswitch and ClientUI runtime license

Microsoft Lightswitch and ClientUI runtime license

jimmyps — Mon, 16 May 2011 23:00:48 GMT

Peter,

That's interesting! Do you have a working sample that we can investigate on?

Thanks,
Jimmy

Microsoft Lightswitch and ClientUI runtime license

pavritch — Mon, 16 May 2011 22:55:48 GMT

Jimmy,

I posed the same question to the Lightswitch team and here is their response:

        "The root UI of a LightSwitch application is part of the common runtime,
        so you will not be able to add the license file into the same assembly the
        root UI is found in."

You can find the thread for this here:
http://social.msdn.microsoft.com/Forums/en-US/lightswitchgeneral/thread/889bb76f-60bd-4d6d-a5c7-35e35d2f2ac9/

Lightswitch does allow for adding references to other assemblies to the xap file. In fact, they encourage developers to create custom controls. If your library could search for the license file in a self-developed assembly, then it would get around the problem. In all other respects, your controls function just fine in Lightswitch.

Now that we have an answer, for the moment I'll stick to standard controls. But I do look forward to you folks supporting lightswitch in a future update.

Peter

Microsoft Lightswitch and ClientUI runtime license

jimmyps — Mon, 16 May 2011 11:53:56 GMT

Dear Peter,

Theoritically, the licensing should work in any compatible container that is used as the root visual. It might fail if Lightswitch used certain containers that are not native to Silverlight.

Yes, we'd be interested to investigate the licensing issue further and possibly include full support for Lightswitch in the upcoming service pack release. Please attach a simple sample that replicates the problem.

Your contribution is highly appreciated. Thanks!

Best,
Jimmy

Microsoft Lightswitch and ClientUI runtime license

pavritch — Fri, 13 May 2011 19:32:09 GMT

Hi Handy,

Lightswitch is a silverlight application generator. It produces several assemblies and I'm believing that the assembly with the root visual is not one that it builds for me...but rather one that is part of their common runtime. That part isn't documented so it's hard to know for sure how all the generated pieces fit together.

http://www.microsoft.com/visualstudio/en-us/lightswitch/

I have tried attaching the license to the assembly it builds with my custom screens, and also to the external assembly I produce and reference from the main generator - no luck on either.

I'm familiar in general with your licensing procedure and have it running successfully on my traditional silverlight apps.

Microsoft is making a big push on this tool. They seem to be putting a lot of manpower on it. Your controls are fully compatible with it - it's just the licensing that needs to be figured out.

Does is have to be the assembly with the root visual? Or will any assembly work? Because if their root visual comes from the common runtime they provide, this might pose a problem.

I could put together a small app for you - but you would need to install Lightswitch Beta 2 to compile it.

Cheers,

Peter

Microsoft Lightswitch and ClientUI runtime license

handy@intersoftpt.com — Fri, 13 May 2011 03:04:35 GMT

Hello Peter,

Normally, to generate licenses.islicx, you need to point into your project assemblies.
Example, ProjectName is "ClientUIDesktopApp1", the assemblies should be "ClientUIDesktopApp1.dll".
When build in LightSwitch, would the name be changed?
If not, please build and ensure your LightSwitch project is already final or does not have any changes anymore before generate the runtime.
After that, set your license.islicx as EmbededResources. You also need to pay attention about RunTime license key. It is different with License key which you used to register the product.
Also, carefully when insert RunTime license key. Please ensure it correctly and does not have " " before or after the license.

Regards,
Handy

Microsoft Lightswitch and ClientUI runtime license

pavritch — Thu, 12 May 2011 16:30:44 GMT

I'm attempting to use ClientUI components to create custom GUI for a Microsoft Lightswitch Beta 2 application.

The instructions for ClientUI licensing states to apply the license to the SL assembly which contains the root visuals.

However, Lightswitch creates a quite a number of assemblies automatically and it's hard to know which one is the true runtime root. When using the runtime license manager, which assembly is the correct one to reference in the file picker?

My custom GUI is located in a separate assembly and I tried using that one as the reference assembly for licensing and it didn't seem to work - the deployed code still showed a message that the product was unlicensed.

Thank you,

Peter