I have seen problems in the past with copy local, particularly with using msbuild. It goes like this:
Assembly B.dll depends on Assembly A.dll Assembly C.dll also depends on Assembly A.dll and Assembly B.dll B -> A has copy local = true C -> A has copy local = false When compiling a solution using msbuild, Assembly A.dll appears in the compiled output of both B and C. The copy local setting should exclude your assembly from the xap, but the build process might be getting confused with multiple copy local settings. If you set the build output level to verbose you may be able to diagnose why your assembly is being copied to the output. Regards, Colin Savage -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Thursday, 10 February 2011 3:40 PM To: 'ozSilverlight' Subject: RE: Dynamic assembly loading Howdy, I should have mentioned that I'm not using MEF or Prism or the like, as my needs are modest and I don't want dependencies on more frameworks. I'm simply firing off some WebClient OpenReadAsync() calls and feeding the returned streams into AssemblyPart Load(), the code is short and clear and it worked first time. I've been searching and searching, but everyone says simply putting "Copy Local" to false on the references will keep them out of the deployed xap file. Not for me ... I have purged all of the binaries out of my solution many times over, restarted, double checked the references and their properties, but no matter what I do the offending DLLs get included in the XAP file. I've now wasted 3 hours on this idiocy. I can only come to your Perth presentation on a first class flight due to a bad back, just post me the ticket. 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
