Another option is to look at Prism. We're using that. Shell downloads and then modules download as required or when available (after the initial shell has downloaded). It comes with some other stuff such as publish/subscribe to enable communication between parts of the app.
Its more a pattern than a framework but provides an implementation. (also uses Unity). It would require a fair bit of work to implement (from memory I spent three days or so, but as I was already following a lot of the pattern it was fairly easy to replace my code with theirs). You can also download dll's in the background and load them dynamically (which is what I was doing before switching to Prism) good luck, Stephen On Wed, Apr 14, 2010 at 1:32 PM, Greg Keogh <[email protected]> wrote: > Hi Asheesh, > > > > My first test of moving the images to “site of origin” worked nicely, as no > code changes are needed. The XAP file reduced from about 2MB to 800KB and > you can feel the loading speed improvement. > > > > However, I have noticed that some later controls load more slowly first > time as new Tree control images are loaded. This seems to be a trivial > problem though. > > > > I forgot that MEF now gets parts from XAPs. I’ll read the documentation on > that feature. > > > > Thanks > > Greg > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > >
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
