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

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

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