XAP Partitioning

Mar 30, 2010 at 4:44 PM

I'd like to use XAP partitioning in my app for two reasons:  to speed the initial load and to allow runtime updates on the server for new UI widgets.  Loading new widgets as they are needed asynchronously in the background will yield performance gains, but arn't there some situations where I'm downloading more content than I would otherwise?  See my imperfect example below that shows how the DataStructure assembly and ServiceLayer assembly have to be included in both XAPs.  Is there any way to avoid them being downloaded to the client twice (once in each XAP)? 

Original App:

Bootstrapper.xap:
Bootstrapper.dll
UIControls.dll
DataStructures.dll
AdditionalUIControls.dll
ServiceLayer.dll

After Partitioning:
Bootstrapper.xap:
Bootstrapper.dll
UIControls.dll
DataStructures.dll
ServiceLayer.dll

AdditionalUIControls.xap:
AdditionalUIControls.dll
DataStructures.dll
ServiceLayer.dll