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.




Labels:

Comments

Post a Comment

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...
Post a Comment
Read more

WebMatrix-The Swiss Army knife from Microsoft

  What’s more in store for Web developers, ASP.Net 4.5(with full support for HTML 5 , CSS 3 amd Javascript) and to complement it, is the new awesome tool-WebMatrix. WebMatrix combines five products in one, letting you install, develop, optimize, deploy and manage your sites and databases. With support for the latest web standards like HTML5 & CSS3, multiple frameworks like ASP.NET & PHP, and multiple database engines like MySQL & SQL Server ..and what’s even better…it FREE!! ! ( Download Webmatrix ). To learn more about webmatrix, I recomment the following video. WebMatrix-An intro The tools promises a lot and I have already downloaded a copy and started playing with it. Hope the information  here is useful. Till next we connect…. Happy Learning.
Post a Comment
Read more

WPF Overview-Part-II

This post is in continuation to the last post. In this Post I’ll be exploring the Dependency Properties Dependency properties are similar to CLR properties with more advanced and complex features. The main difference between the CLR properties and dependency properties is, that the value of a normal .NET property is read directly from a private member in your class, whereas the value of a DependencyProperty is resolved dynamically when calling the GetValue() method that is inherited from DependencyObject . In case this description did not make sense, no need to worry, It will become clear by the time you reach end of this article. How the Value is Resolved in Dependency properties Every time a dependency property is accessed, it internally resolves the value by following the precedence from high to low. It checks if a local value is available, if not, check if a custom style trigger is active and I the similar manner continues until it finds a value. At last the default value is alwa...
Post a Comment
Read more