Step by Step to discuss Application Library Caching in Silverlight 4

Introduction

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. 

Read more: Codeproject

Posted via email from Jasper-net