Have a look at this http://development-guides.silverbaylabs.org/Video/Dynamically-Loading-.Dlls-in-Silverlight It seems to cover how I started off doing it on a project last year. I started off copying how Prism does it (it's a pattern with some helper dll's essentially) and then later we swapped in the Prism helpers. That was pretty easy as I'd named everything closely with Prism.
So you can do it yourself or use a framework such as Prism. I've heard it said Prism is quite large/bloated compared to some other frameworks. I've not yet had a chance to look at the others, I like to do things myself until the need arises to use someone elses framework. Its a double edged sword, it does what you want but comes with their bugs. I'll be looking at MVVM lite over the next few weeks. May even do a demo at next Perth Silverlight user group. (more than welcome to fly over to visit hehe) have fun! On Thu, Feb 10, 2011 at 11:41 AM, Greg Keogh <[email protected]> wrote: > Folks, after years of avoiding the need, I finally have to async load some > large DLLs. I have two charting libraries to reference and their total size > is causing slow app loading. > > I have placed the guilty DLLs in the ClientBin folder and I can see them > async loading correctly. But ... how do I let them be referenced in the > project for compilation, but keep them out of the app XAP file for deploy? > > I tried setting Copy Local = false for the two references, but that has no > effect. > > Cheers, > 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
