Hello,

Does the dll come from another library WebProject application? Or is it from Silverlight Web Aplication?
I think if it is from another Silverlight Web Application, you could not refer into .dll itself, but it should .xap itself. Regarding this scenario, I would like to discuss with our developer teams. I will let you know asap after I got the response.

Regards,
Handy

Hi,

Our DLL were created as "Silverlight Class Library". They are part of the Silverlight project (the silverlight application has a dependency on them).

Our concern is about the naming convention on this call :

UXShell.Current.RootApplication.CreateInstance(viewType)

What should be the value of viewType in our case ? « Assembly.View » ?  « Assembly/View » ? Something else ?

Hi Sebastien,

I supposed that you have created the ApplicationPackage for the Silverlight project you wish to load on demand.

In this case, make sure the EntryPointAssembly or the MainAssembly attribute in the SAFMetaData.xml that resides in your "external" Silverlight project has been properly set.

The type that you passed to the CreateInstance should be the FQDN of the class type (i.e., SilverlightApp1.Class1), and this class should be found in the assembly you specified in either the EntryPointAssembly/MainAssembly described above.

For more information about ApplicationPackage, please refer to ClientUI Application Framework Overview.

Hope this helps,
Jimmy

Hi,

We found a way to resolve our issue.

We changed the "public static IModalWindow GetInstance(string viewType)" method like this :

Original :

        public static IModalWindow GetInstance(string viewType)

        {

            return UXShell.Current.RootApplication.CreateInstance(viewType) as IModalWindow;

        }