Skip to main content

PRISM-Video Series

Although I plan to write my own articles about  the topic, however this time I am in  some sort of hurry to get started with development, so i am relying on Microsoft resources to get me(and of-course you) started.

PRSM, as you will find across the web, is nothing more than guidelines for developing modular applications(Component based appications).
This in simple terms, means creating loosely coupled applications that follow SOLID principles laid down in Microsoft patterns and practices book.

PRISM relies on  Unity framework (downloadable from codeplex).
Details about the installation and sample code, quickstarts are a part of the download.

Briefly , PRISM (via UNITY) requires the code to have the following Components and their Co-ordinated efforts results in Modular application
1. Bootstrapper
2. Shell
3. Regions
4. Modules
5. Views

This Simple diagram depicts how they interact with each-other or rather how they should actaully interact.
in the diagram IOC = Inversion of Control

Theoretically this looks good,
Now lets go through these videos(9 parts) to better understand PRISM.
Part 1


Part 2-Dependency  Injection with Unity


 Part 3-Modularity with Prism



Part 4-Unity BootStrapper



Part 5-Moving to Modular Silverlight Project



Part-6-Shells, Regions, Views


Part-7-Commands



Part 8-Loosely Coupled Events



Part 9-Sharing Data with Region Contexts



Disclaimer: These videos are a part of channel 9 video tutorials by Microsoft and has been used here  with the sole intention of knowledge sharing.




Hope this tutorial is useful...
Till next time we connect...
Happy Learning.




Comments

Popular posts from this blog

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...

WCF..Why Communication Foundation?

WCF (Basics..for building effective Services) WCF:  Windows Communication Foundation It includes a collection of of .NET distributed technologies that have existed for long , but never got grouped under one name. WCF can be considered as collection of the following technologies. Web Services(ASMX) NET Enterprise Services MSMQ .NET Remoting Code written in WCF can interact across components, applications and systems. WCF is in accordance with SOA (Service Oriented Architecture). Following Sections provide the details of these ABCs. Addresses In WCF, every service has a unique address. The address provides two important elements A)     Location of the service B)      Transport protocol or transport schema used to communicate with the service.  The location indicates the name of the target machine, site, or network; a communication port, pipe, or queue; and an optional specific path or URI. WCF supports th...

Covariance and Contravariance-General Discussion

If you have just started the exploration of .Net Framework 4.0, two terms namely Covariance and Contravariance might have been heard. The concept that these terms encapsulate are used by most developer almost daily, however there has never been any botheration about the terminologies. Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them. Enough philosophy, let’s get to the business. Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further. Invariance: Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either ...