Prism v2 - Composite Application Guidance for WPF and Silverlight | The Continuum Show

BERTOLOF1962
This is me infront of my pc.

This was a very good demonstration of Prism version 2, for Composite Application Guidance for WPF and Silverlight! When I have just downloaded and install this brand new program on my harddrive, so shall I take my time to learn myself how to use it of course of this simple reason: I have never use it before so this shall be the very first time when I am a beginner with this kind of program. But I hope to do this as soon as possible.

zinovate

Rock on guys, sweet release and the addition of the Silverlight support is AWESOME.
Thanks guys.

Maddus Mattus
Do, or do not. There is no try. - Yoda

In reply to zinovate

#Feb 18th @ 7:53 PM

Can't wait to use it in future projects!

vesuvius
Das Glasperlenspiel

It really would have been better had you jumped into a code demo. I watched a Brian Noyes demo on dnrtv which was excellent as there is a demonstration into how two loosely coupled user controls can be made into publishers and subscribers, the code is very elegant (not like the mess left in Windows Forms).

The MVVM stuff with Karl [Shiftlett] is cool, but this even more so?

Why is it that Patterns and Practices call this "Model View Presenter" but Josh Smith etc. go with Model View View Model, how about just calling it one thing please guys?

AdamKinney
Agent of Change

In reply to vesuvius

#Feb 19th @ 6:44 AM

The names are different because the patterns are different. Check out Josh Smith's MVVM article for a full explaination but here's a quote:

"Unlike the Presenter in MVP, a ViewModel does not need a reference to a view"

stormideas
stormideas - expertly crafted web applications

This is really useful stuff. I've spent the last few months putting together a fairly large Silverlight 2 collaboration application called colaab:

http://www.colaab.com

And I've run into many of the problems that the Prism release seeks to address and if you're looking at building complex RIAs using Silverlight you could do a lot worse than using it as a starting point.

There's also a good article on MVVM in Silverlight in this months MSDN Magazine:

http://msdn.microsoft.com/en-us/magazine/dd458800.aspx

Thanks,

Bob