Hello Balachander,

Actually, you need to follow our approaches, not DevForce. We have a similiar code that shows LoadOnDemand App in our ClientUISamples, App.xaml.cs. We ever tested the code along with DevForce and it works fine. Here is the snippet code.

private void DiscoverAvailablePackages()
        {
            UXShell.Current.IsInitializing = true;
            ResourceDownloader downloader = new ResourceDownloader();
            downloader.Downloaded += (o, e) =>
            {
                Stream stream = (Stream)e.Resource;
                XDocument x = XDocument.Load(stream);
                var packages = from package in x.Descendants("ApplicationPackage") select package;
                foreach (XElement package in packages)
                {
                    using (StringWriter writer = new StringWriter())
                    {
                        package.Save(writer);
                        UXShell.Current.Applications.Add(ApplicationPackage.Parse(writer.GetStringBuilder().ToString()));
                        
                    IdeaBlade.Core.Composition.CompositionHost.Add(ApplicationPackage.Source);
                    }
                }
                UXShell.Current.IsInitializing = false;
            };
            downloader.Failed += (o, e) =>
            {
                throw e.Error;
            };
            downloader.Download(new Uri("Applications.packages", UriKind.RelativeOrAbsolute));
        }

Regards,
Handy

Hi Handy Surya,

Thanks a lot for the answer which is spot on and the code snippet .

I guess I do not need to write the piece of code(shown below)  in the shell Downloaded event handler but rather do it when the xap is downloaded.

IdeaBlade.Core.Composition.CompositionHost.Add(ApplicationPackage.Source);

Could you also enlighten me why MEF is not used in ClientUI ?

Regards

Balachander

Hello,

I will need to discuss with our developer about why MEF is not used in ClientUI. I will let you know the update.

Regards,
Handy

Hello Jimmy,

Thanks once again for the insight into the design perspective of choosing to not use MEF but design your own extensibility API !!

 

Regards

Balachander

Hello Balachander,

We require our solution to be Silverlight version independence which is why we don't want to design our extensibility API based on MEF. Currently, our API works in Silverlight 3, 4 and 5. This also allows our solution to provide unified API to other platforms like WPF and Windows Phone 7.

Hope this helps,
Jimmy