Love TypeScript. This is important work.
Jun 26, 2013 at 2:54 AM
Here is an excellent description of the deployment catalog including information on how to create a XAP that references assemblies, but does not include them (copy local = false).
The main caveat is that a XAP that does include these assemblies must already be loaded before loading such a XAP (otherwise when MEF enumerates the contained types, Silverlight will throw an exception about the assembly or referenced assemblies not being loaded).
All of this is AWESOME...
Question: is there a way to avoid downloading assemblies that are already included in the base XAP or in one of the dynamically downloaded XAPs?
Related Question: can I now (in Silverlight 4) enumerate the assemblies that an assembly references?