Search

There are two ways to pass parameters to a Silverlight application:

• Using the querystring of the containing HTML/ASP.NET page
• Using the InitParams attribute of the object tag that hosts the XAP file

I’ve found multiple posts on the web explaining how to sign a XAP file, including this one. In Silverlight 4, a XAP file must be signed in order to let an out of browser application update itself and to show the user a more friendly installation dialog when installing an elevated trust application. The  process for digitally signing a  XAP file explained on the web, includes using a post build event in which “signtool.exe” is called. With the new Silverlight 4 RC2 tools for Visual Studio 2010, there is another way to sign your XAP file…

Introduction

My XAP file is 5 Mb size, is that bad?

Unfortunately that’s a usual question for lot of new Silverlight developers, … you start coding you Silverlight app everything is easy to do, you can use lot of powerful third parties stuff, and finally you end up with an awesome application that runs quite well under Cassini / localhost, then you a realize that…

Well...

In this post Al Pascual plays a little with the new Managed Extensibility Framework MEF for short library.

I have many questions after the first application, even that everything works, the piping of the attributes are a little complicated, thanks to Brad Abrams post to help me, yet I have try to avoid using the collection to import the XAP UserControl without any success. I cannot find the reason why we need a collection to import one XAP file class.

I just had to do this and figure I'll document the steps. It isn't rocket science, but here's the story.

First, you need to place a clientaccesspolicy.xml or a crossdomain.xml file at the root of your server. Read this MSDN documentation for more.

The preloader application will load first to provide some immediate feedback to the user and then begin downloading the main application asynchronously in the background.  As soon as the main application has finished downloading, the preloader application will instantiate and then inject the main application into its visual tree.