Search

In this article, Mahesh Sabnis explains how to use DelegateCommand for implementing loosely coupled applications in Silverlight 4 using Prism 4.

Source: Dot Net Curry

For developing loosely coupled applications using Silverlight 4 or WPF, it is suggested that Prism 4 libraries be used in most scenarios. These libraries provide various features like Modularity, UI Composition, EventAggregator, MVVM using DelegateCommand and CompositeCommand etc. All these features are important for building Composite applications.

Brian Noyes shows you how to use the DataTemplateSelector class in Prism 4.

Source: Brian Noyes' Blog

DataTemplates in WPF have a very important feature: the DataType property that allows DataTemplates to be automatically applied to a data bound object based on its type. This feature is very similar to the implicit styles capability that WPF has had since the start that is a new feature in Silverlight 4.

Unfortunately Silverlight is still lacking this feature. In Silverlight, you have to associated a single data template with a data bound control through its template property (ItemTemplate for ItemsControl and ContentTemplate for ContentControl). When you want to bind to a heterogeneous collection of objects (that all share a common base class or interface that the collection is defined in terms of), you are kind of stuck in Silverlight if you want to write specific templates per derived type.

In this tutorial, Sacha Barber shows how to easily use CinchV2 with Prism 4.

Source: The Code Project

I know some of you will know that I am WPF lover, and that I have my own MVVM framework out there called Cinch, and that I not so long ago published a whole series of articles on V2 of Cinch, and are probably bored to death of it, well from time to time me too, but someone asked me how easy it would be to get Cinch to work with PRISM, and I just had to give it a try.

So this article will demonstrate how easy it is to use my own MVVM framework Cinch V2 with all the good bits a peices you have grown to love from the Microsoft composite WPF/SL application block A.K.A : PRISM.

In this article, Mahesh Sabnis explains the module loading features in Silverlight 4 when using Prism.

Source: Dot Net Curry

Prism provides guidance, in the form of quick starts and a set of libraries consisting patterns, for developing composite applications using Silverlight, WPF and Windows Phone 7. These libraries help in designing and building WPF and Silverlight client applications which are modular, easy to build and flexible to maintain.

In the article, Mahesh Sabnis demonstrates how to use Prism in Silverlight by creating a sample application.

Source: Dot Net Curry

With an increasing popularity and availability of advanced features, Silverlight is being used by many developers to create rich browser applications as well as Line-Of-Business (LOB) applications. The focus is on creating rich, flexible, easy-to-maintain application keeping in mind the separation of concerns and loose coupling.

Prism is a guidance designed and developed by Microsoft which provides a set of libraries consisting of patterns for developing composite applications using Silverlight, WPF and Windows Phone 7. These libraries help in designing and building WPF and Silverlight client applications which are easy and flexible to maintain. The current version of Prism as of this writing is Prism 4.

Brian Noyes explains about the changes made in Prism 4 regarding commands.

Source: Brian Noyes' Blog

One small change that was made in Prism 4 was to update the DelegateCommand class to deal with command parameters a little more cleanly, and also to update the weak reference handling inside the DelegateCommand to work correctly based on the way Silverlight 4 implemented command hookup as opposed to WPF.

This blog pots of Lee is on Custom Commands in Silverlight and Prism 4.

Source: Lee's corner

Silverlight 4 includes commanding support for ButtonBase classes, but for anything else we would need to write a little bit of code.

There is a nice section here on how to extend this to other situations. Here is a quick sample on how to create command support for MouseLeftButtonDown on an UIElement. You can download the code from here.

Brian Noyes talks about some of the options that Prism 4 has when you wnat to show a prompt to the user .

Source: Brian Noyes's Blog

This post assumes you are familiar with the MVVM pattern and the reasons why you would want to separate your view and your view model, as well as the standard structure of the MVVM pattern (View.DataContext = ViewModel). The key things to keep in mind for what I am going to cover here is the it is the view’s responsibility to determine the visual rendering of a part of the application functionality, it is the view model’s job to encapsulate the state and logic that support that view without being coupled to the view too tightly and without specifying visual aspects directly itself. When doing MVVM right, you should be able to hand the view’s XAML over to a designer, allow them to change every single element in there if they choose to, and not break the application as long as they maintain the bindings that were in the view so they display things in similar ways.

We tweet all news and content updates - follow us on Twitter!