Search

In this article, Mahesh Sabnis has explained how to define custom command behavior to the ListBox control using Silverlight and Prism 4.

Source: Dot Net Curry

Prism 4 is an excellent pattern provided to us for developing Line-of-Business (LOB) enterprise applications using Silverlight 4.0 as well as WPF 4.0. Implementing XAML only development is an excellent feature where the code-behind can be completely reduced or removed. In a typical MVVM architecture, to process the data which is send by the UI (by the ViewModel), we have been provided with an excellent Commanding concept. Command is an object which implements an ICommand interface.

With this EventAggregator wrapper created by Shimmy Weitzhandler, you can easily get rid of the CompositePresentationEvent<T> and control the EventAggregator instance.

Source: Shimmy on .NET

The Prism EventAggregator really is too verbose.

To subscribe to an event you have to

• Instantiate (or get the current) an instance of EventAggregator which is somehow complex for itself, especially when you want to use simple MVVM, without Unity or MEF.
• Get thru the redundant CompositePresentationEvent<TEvent> and its methods.

SilverlightShow Webinar presenter Brian Noyes (check the recent webinar by Brian on WCF RIA Services Validation) is one of the authors of the new book on Prism 4: Developer's Guide to Microsoft Prism 4: Building Modular MVVM Applications with Windows Presentation Foundation and Microsoft Silverlight.

This guide provides everything you need to get started with Prism and to use it to create flexible, maintainable Windows® Presentation Foundation (WPF) and Microsoft Silverlight® 4.0 applications.

It can be challenging to design and build WPF or Silverlight client applications that are flexible, maintainable, and that can evolve over time based on changing requirements. These kinds of applications require a loosely coupled modular architecture that allows individual parts of the application to be independently developed and tested, allowing the application to be modified or extended later on. Additionally, the architecture should promote testability, code re-use, and flexibility.

Prism helps you to design and build flexible and maintainable WPF and Silverlight applications by using design patterns that support important architectural design principles, such as separation of concerns and loose coupling. This guide helps you understand these design patterns and describes how you can use Prism to implement them in your WPF or Silverlight applications.

This guide will show you how to use Prism to implement the Model-View-View-Model (MVVM) pattern in your application, and how to use it along with commands and interaction requests to encapsulate application logic and make it testable. It will show you how to split an application into separate functional modules that can communicate through loosely coupled events, and how to integrate those modules into the overall application. It will show you how to dynamically construct a flexible user interface by using regions, and how to implement rich navigation across a modular application. Prism allows you to use these design patterns together or in isolation, depending on your particular application requirements.

Karl Shifflett has blogged how to use the Unity Container with Prism 4 Region Navigation and the Silverlight Frame Navigation API’s.

Source: .NET Developer Guidance

I have had several requests to demonstrate how to use Unity with Prism 4 Region Navigation and the Silverlight Frame Navigation framework.

The primary purpose of this blog post is to provide an example of using Unity for dependency resolution when writing a Silverlight application that also uses Prism 4 Region Navigation and the Silverlight Frame Navigation framework.

In this post, Alex van Beek not only discusses the View and ViewModel base classes, but also shares some extra background information about PRISM.

Source: Alex van Beek's Blog

When you are developing Silverlight applications following the MVVM pattern, you will eventually run into the fact that you’ll have to create a base class for your viewmodel classes. This post will show how to create a useful base class for your viewmodel classes and also how to create a base class for your view classes, which a lot of developers don’t do. In the end, I will show how to wire everything up.

Here are the slides and samples from the talk of Thomas Martinsen and Martin Jespen about Silverlight patterns and framework at the monthly Silverlight Usergroup meeting in Denmark.

Source: XAMLGeek

I the first part of the talk, Martin showed the differences between MEF and Unity and wrapped up by showing some of the possibilities in PRISM. [...]

In the second part of the talk, I showed how to expose an OData feed using a WCF DataService and access the data from a Silverlight application.

Mike Taulty has published some resources from the UK TechDays online sessions.

Source: Mike Taulty's Blog

At the UK TechDays online conference last week there were a number of sessions around Silverlight and Windows that I wanted to provide follow-up resources on here.

Damian Schenkelman has an example on how to load modules that were packaged for remote module loading in a Silverlight OOB app.

Source: Damian Schenkelman's Blog

I created this sample a couple of months ago, and I thought might be useful for others. Here you can download the sample I put together using the Modularity QS from Prism 4. You can also download the necessary files separately (OOBModuleManager.cs and CachingXapModuleTypeLoader.cs)

Brian Noyes posted the sides and demos from his talks at DevConnections on RIA Services, Prism and WCF Client Security.

Source: Brian Noyes' Blog

To those who attended, thanks for the great participation and questions!
To anyone who wants the slides and code, you can find those below.

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