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-REST Services-Part-II

HOW REST is implemented in WCF Part-I of the series explored the REST conceptually and this post will explore how REST is implemented in WCF. For REST implementation in WCF, 2 new attributes namely WebGetAttribute and WebInvokeAttribute are introduced in WCF along with a URI template mechanism that enables you to declare the URI and verb to which each method is going to respond. The infrastructure comes in the form of a binding ( WebHttpBinding ) and a behavior ( WebHttpBehavior ) that provide the correct networking stack for using REST. Also, there is some hosting infrastructure help from a custom Service¬Host ( WebServiceHost ) and a ServiceHostFactory ( WebServiceHostFactory ). How WCF Routes messages WCF routes network messages to methods on instances of the classes defined as implementations of the service. Default behavior ( Dispatching ) for WCF is to do this routing based on the concept of action. For this dispatching to work, an action needs to be present in ev...

WPF –ElementHost

In response to WPF overview-Part-I , one of my friends and a .Net enthusiast herself, requested for details on ElementHost Class of WPF (this class gave her nightmares in not getting the Children attached to it). This might be true for many other developers who are specialized in Web Applications and  have lesser exposure to windows development. As a breather to all those folks, I am here exploring this class with sincere hopes that it will provide a good insight to the class.   ElementHost as described in MSDN is “a Windows Forms control that can be used to host a Windows Presentation Foundation (WPF) element” is located under System.Windows.Forms.Integration namespace . The members of this class have details available at this location . Why is this Class used? ElementHost control is used to place a WPF UIElement on to the Windows Forms control or form. In simple words, if a developer is using the traditional Windows forms and intends to use WPF controls, this control (class) is used...