All Visual Studio blogs in one place

AddThis Social Bookmark Button
source: In this tutorial I'll demonstrate how to split a Windows Phone app into multiple assemblies - which are loaded on-demand, not on startup - when using Caliburn.Micro. The Problem If you want to use Caliburn.Micro and you also want to split the app into multiple assemblies, the problems starts with the app's bootstrapper and IOC. Given the scenario that we have the following assemblies: LoadAssembliesOnDemand - The main assembly, which starts the app. Module1 - Another assembly which will contains views (pages and user
controls) and view models Module2 - Another assembly with views and view models Now if we configure the Caliburn.Micro's container as we usually do, the code ends up looking like the following: container.PerRequest(); container.PerRequest(); container.PerRequest(); And here's the debug output from our app's startup: As you can see, configuring the container as we did forces the platform to load both the Module1 and Module2 assemblies, even though we don't need them yet. What we need is a way to configure the IOC...(Read whole news on source site)



Enter your email address:

Delivered by FeedBurner

Increase your website traffic with


Anti-spam: How many eyes has a typical person?

Follow us on FB

Home : Blog List : WindowsPhoneGeek : Windows Phone: Splitting Application to Multiple Assemblies when using Caliburn.Micro