ViewModel 1st Child Container PRISM Navigation

I have recently just started work on a greenfield WPF project using PRISM 4. When I started I knew that we would be used a workspace driven design and that I wanted to go VM first route, and that I wanted to make use of PRISMs navigation API.

I was also pretty keen to try and use child IOC containers for my workspaces where possible, such that the life cycle of the child container could be coupled to the VM that would be shown for a workspace. That way when the VM was closed the child container and all its dependencies would also be cleaned up.

So I had a bit of a play around with PRISM and managed to get that work out quite nicely. If this sounds like it would be of use to you, you can learn more by reading the full article, which is available right here:



  1. Hi Sascha,

    I love all you Blogposts and i am reading your articles for a log time now.

    I also want to share a super fantastic framework that i am currently using.

    It is a awesome combination of MEF / Caliburn.Micro / EntityFramework 5 to create very flexible Enterprise Applications with loosly coupled components.

    Cocktail also has a navigator class, that extends the mechanisms of caliburn.micro.

    you really have to take a look into that framework! i am super happy with the framework an i feel like a developer on steroids!

    happy coding šŸ˜‰


    1. Dirty something went wrong with my blog, only just saw this comment, looks cool, sorry for delay


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s