Follow us on X (Twitter)  Like us on Facebook  Connect with us on LinkedIn  Subscribe to our YouTube Channel  Subscribe to our WhatsApp Group

Sometime your Silverlight application becomes too larger and creates a bigger XAP file. This causes issue while loading your XAP file for the first time as it increases the loading time for downloading the XAp. So, what will you do in this case? There is one answer: split your application in multiple projects which will create multiple XAPs and then use On Demand downloading feature.


Absolutely right, but you may sometime include 3rd party assembly references. In such case, storing them in a separate XAP and writing the code for downloading them on demand will be another hectic. So, what's the easy process? In this article we will learn the same. Read to know more and provide your feedback in case you need more information.





Assembly caching is not a new thing in Silverlight 4. It was present since Silverlight 3. Today I got a chance to look into it and thought to share the same with depth details to you.


So, what is Application library caching? We all know about the on demand download of XAP. To do this, we need to write code for downloading the external xap files using WebClient. Application Library caching does the similar thing for you very easily. Suppose, if you have a bigger application and used a huge 3rd party libraries, this easy step will help you make a separate zip file with them which can be downloaded on demand without writing any additional code.


Many people don't know about it and hence let's start describing that here.



Step 1 - Digging inside XAP:

First of all, we will create a small Silverlight Application project. To do this, open your Visual Studio and create that.





Once you done creating the project, in Solution Explorer you will see that it has some default references to some assembly files. Once you build the project, it will create a .XAP file for you. Here is a screenshot of the same:




You can see that, it creates the XAP file in the client bin directory. It creates a single XAP irrespective of no. of assembly files referenced to that project and unnecessarily increases the size of XAP file whether it requires those or not.


To see the contents inside the XAP, go to the ClientBin folder. There you will find the XAP output of your Silverlight application.




As you all know that, all the XAP files are nothing but a ZIP file, hence you can easily convert it to a Zip file by renaming it's extension.





Open the ZIP file. Inside that, you will find "AppManifest.xaml" (which stores the referenced Assembly information), dll output of your project and all other referenced assemblies. If you add more 3rd party assembly reference in your solution, this list will increase.





To know details of that, open the AppManifest.xaml file in a text editor. Have a look into the below screenshot:





You will notice that, it has all the referenced dll information as Assembly part, entry point and required runtime version. Assembly parts tells to load the referred assembly directly from the XAP.



Step 2 - Working with more Assemblies:

Just visualize what we demonstrated in the first step. Now, we will add some additional dll reference in our project. To do that, right click on your project and click "Add Reference'. Now from the add reference dialog, select some 3rd party dlls and include them in your project.


For the demonstration, we will add some theming dlls in our solution. To do this, search for "theme" and you will see a list of theming dlls in the add reference dialog. Chose some of them and add into the project.





Once you add them, you will notice that the selected assemblies are now part of your project (see the figure below):





Now, build your solution and open the new XAP file (rename it to a ZIP). You will see that all the new referenced dlls are now part of your XAP. See the below screenshot, which will give you better information:





Let us open the "AppManifest.xaml" and see what it contains now. Wow, it contains all those additional dll entries as AssemblyPart and tells to load them from the XAP itself.





This actually increases the XAP size and makes your application little bulky. Thus increases initial loading time of your application.



Step 3 - Using Application Library Caching:

To overcome this, let us change the setting of our project to use the Application library caching feature now. Go to your project properties panel. In the Silverlight tab, you will find a checkbox called "Reduce XAP size by using application library caching". Check this as shown below:





Now build your project once again and you will see, it will create as many .ZIP files as the count of external assemblies as shown below. You will also notice that, it creates a single zip for a single referred dll assembly.





Let us go into the deep to lookout the Application Manifest. Go to the output directory "ClientBin". You will see a single XAP file with a no. of ZIP files shown below:





Each ZIP contains a single dll file here. Rename and open the XAP file. Open the AppManifest.xaml from the XAP.





Here you will notice a single AssemblyPart pointing to your original project output and rest of the dll references are now moved to ExternalParts. They are now pointing to the Zip files instead of the actual dlls.


Now, when you run your application, it will only download the XAP file which contains only the main resources. Rest of the dll ZIP will be downloaded on demand whenever require by your application.


Hope, this information will help you to understand the library caching feature of Silverlight and give you the chance to use it in your application. Let me know, in case you need further information on that.

Have a question? Or, a comment? Let's Discuss it below...


Thank you for visiting our website!

We value your engagement and would love to hear your thoughts. Don't forget to leave a comment below to share your feedback, opinions, or questions.

We believe in fostering an interactive and inclusive community, and your comments play a crucial role in creating that environment.