1. Remove the images from the XAP and web-deploy them. You'd have to move your XAP outside the clientbin (one level up) 2. Use MEF
On Wed, Apr 14, 2010 at 2:33 PM, Greg Keogh <[email protected]> wrote: > I’ve finally hit the point where the loading speed of the SL3 app is > becoming an issue. On my LAN it takes 3-5 seconds to load, but it takes a > frightening 30 seconds or more from a different office over their ADSL-1 > connection. My XAP file contains a fr-FR locale for globalisation testing > and I’m using some Liquid and Visifire controls. Below I’ve pasted the > contents of the XAP file in size order. The size is distributed like this: > > > > Root ~ 2.53 MB > > fr ~ 289 KB > > images ~ 1.2 MB > > TOTAL ~ 4MB > > > > I was hoping that I could simply take a couple of the big DLLs out of the > manifest and async load them as assembly parts, which would have been great > as the big Visifire DLL isn’t need until after you logon and navigate down a > few screens. But it doesn’t look that simple because the size is taken up by > a mix of different things. Just taking the 598 KB Visifire DLL out won’t > make significant difference. As a first experiment I’m going to see if the > images can be removed from the XAP and web-deployed. > > > > This is a lesson that you must not forget deployment size issues in a large > SL app. Some of you must have much larger XAP files than I do, and I’m keen > to hear what tricks or techniques you use to keep app loading speed > tolerable. > > > > Greg > > > > > > *Root folder* > > *fr subfolder* > > > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
<<image002.png>>
<<image001.png>>
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
