Let me first say that I really love what MEF allows me to accomplish in my apps. You get major props in my book!
My question is about composition. I have a Silverlight app using XAP partitioning. For the sake of example let's say I have the XAPs below with both XAPs referencing the same CommonObjects.dll. Then I run my app and load up both XAP
files. The Extensions.XAP satisfies a recomposable import on one of my objects in SilverlightProject1.
Next I make some updates to Extensions.dll and CommonObjects.dll on the server and redeploy Extensions.XAP. When Extensions.XAP is re-deployed that change is persisted to the CompositionContainer via an AggregateCatalog filled with DeploymentCatalogs.
Imports that support recomposition are now recomposed.
At this point my app has two conflicting versions of CommonObjects.dll. One was deployed with SilverlightProject1.XAP (and Extensions.XAP the first time), and the second was deployed with Extensions.XAP the second time it was deployed. Which
version of CommonObjects.dll gets used when the Import is recomposed?
Could you explain a bit about how XAP partitioning works with muliple XAPs containing the same assembly?
Looking forward to your answer.