When your application is small (in size), everyone is happy. The load on the servers is minimal, the load times for the user fly by instantly, and the user starts to use your application within seconds. As your application gets more complex and more assemblies are used, the size of the application will grow. But what if our application is divided into different projects and each project contains a Grid control? Will that mean that each and every time we hit a page, the DLL containing the grid will be loaded to the user? By default, yes.
In order to tackle this issue, we have two options—use assembly caching or create ZIP files ourselves containing assemblies, images, resources and so on.
Using assembly caching is straightforward, and we have already discussed it in Chapter 1, Overview of Silverlight. To recap, all you have to do is right-click on the Silverlight project in Visual Studio 2010, choose Properties, and check the...