PRISM and enterprise level applications.

[Pants]

Chaps,

Is anyone currently developing WPF or Silverlight business applications with PRISM?

If so I'd be interested to hear your thoughts on it - and also if you know of any good teaching material.

Our team is taking on development and 3rd line support for various business applications built this way. So I need to get myself up to speed quickly!

I work mostly on ASP.NET MVC using DDD, Dependency Injection, etc etc... so hopefully this goes some way towards preparing me for the PRISM way of doing things - but it looks properly hardcore from what i've seen so far!

 

[Haircut]

I'm currently working on a project using PRISM 4 with WPF.
We're using an MVVM pattern and PRISM 4 supports this better than the old versions, using it with Unity too, though MS seems to be pushing the MEF way of doing things a bit now.
If you've done anything with a dependency injection container before that bit should all be pretty natural.

PRISM itself has a bit of a learning curve, but it's not too bad once you get your head around the idea of a composite application.

On that front I have to say I'm not wholly convinced of the merits of a fully composite application.
Once you get beyond the simple demo applications that they provide and have menuing, workflow etc. in your application it becomes very difficult to do it in a properly composite way and then you lose some of the benefit of what PRISM provides.

In terms of learning stuff I've found the PRISM documentation to be pretty decent - not sure where else would be good to go to learn it, but I would recommend trying to put together a very simple proof of concept app (a couple of modules with views across a couple of regions sending events to one another should be reasonably easy to knock up) to understand the basic concepts.