Are you running Silverlight 4 and don't need OOB support? Simple solution is the built in application library caching. For external dlls you may need to manually create the exmap. Also I saw you mention they were c1 controls, have you used their XAPOptomiser to trim out unused code instead? I've implimented dynamic assemble loading for an application based on the navigation framework, essentially load each page from a remote dll, it is really quite fiddly to setup and I don't recommend the pain but the model of only loading the code you need as you load that page makes a lot of sence. > From: [email protected] > To: [email protected] > Subject: RE: Dynamic assembly loading > Date: Thu, 10 Feb 2011 17:13:46 +1100 > > Colin, I also suspected some sort of domino effect of dependencies was > causing my DLLs to stay included in the XAP. I'm sure my DLLs are only > referenced in a single project, and that project has Copy Local false. > > I moved the DLLs to a separate folder and referenced them there instead of > under C:\Program Files (x86) as Copy Local false. I cleaned everything, ran > msbuild verbose and had a look at the output. > > The output is contradictory. It says it found the DLLs in my folder and > correctly says they a copy local false. Later it says it will copy the files > from the Program Files folder and then it gets included in the xap. > > There is some influence over the build that I can't detect, possibly taking > references from the Program Files folder when I don't expect it to. > > Oh well, there goes another 5 hours of mostly unpaid work. > > "Everything doesn't work" -- 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
