Array

Contents of Prism for Windows Phone 7 Library

Must Read

How To Stay in Your Home Mortgage Payments-Free For Over 3 Years by Delaying the Foreclosure Process

With the current economic situation, losing your home is a reality. Even though Obama's government activated a number of...

Refinancing Your Home – Typical Closing Costs

When refinancing an existing mortgage, homeowners must be prepared to pay new closing costs, just as they did when...

Government Debt Consolidation Loans – Consolidate Your Federal Student Loan Debts

Are your debts becoming too much of a burden for you? Well, your country can help you deal with...

Prism Library for Windows Phone 7 contains several namespaces that subdivide the artifacts:

  • Microsoft.Practices.Prism. This namespace contains classes concerned with detecting and reacting to change events for properties and objects.
  • Microsoft.Practices.Prism.Commands. This namespace contains classes concerned with binding commands to user interface (UI) objects without requiring the use of code-behind in the view model, and with composing multiple commands.
  • Microsoft.Practices.Prism.Events. This namespace contains classes concerned with subscribing to events and with publishing events on the publisher thread, UI thread, or a background thread.
  • Microsoft.Practices.Prism.ViewModel. This namespace contains classes that help support implementing the view-model portion of the MVVM pattern, such as displaying a template at run time and simplifying the implementation of property change notification.
  • Microsoft.Practices.Prism.Interactivity. This namespace contains classes and custom behaviors concerned with handling interaction and navigation for application bar buttons and with updating the values of view model properties bound to text and password controls.
  • Microsoft.Practices.Prism.Interactivity.InteractionRequest. This namespace contains classes concerned with displaying notifications to users.

The following tables list the main classes in these namespaces and provide a brief description of their usage. They do not include all the
classes in each namespace; they list only those that implement the primary functions of the library. For a full reference to all the Prism
namespaces, see “Prism (Composite Client Application Guidance)” on MSDN (http://www.microsoft.com/prism).

Microsoft.Practices.Prism Namespace

The following table lists the main components in the Microsoft. Practices.Prism namespace. These classes are not used in the Tailspin application.

Microsoft.Practices.Prism Namespace

Microsoft.Practices.Prism.Commands Namespace

The following table lists the main components in the Microsoft. Practices.Prism.Commands namespace.

Microsoft.Practices.Prism.Commands Namespace

For more information about using the DelegateCommand and CompositeCommand classes, see the section, “MVVM,” in “Prism (Composite Application Guidance)” on MSDN (http://www.microsoft.com/prism).

Microsoft.Practices.Prism.Events Namespace

The following table lists the main components in the Microsoft. Practices.Prism.Events namespace. Classes in this namespace support decoupled communication between pieces of an application, such as between two view models. These classes are not used in the Tailspin application.

Microsoft.Practices.Prism.Events NamespaceMicrosoft.Practices.Prism.Events Namespace

For more information about publishing and subscribing to events, see the section, “Communicating between Loosely Coupled Components,” in “Prism (Composite Application Guidance)” on MSDN (http://www.microsoft.com/prism).

Microsoft.Practices.Prism.ViewModel Namespace

The following table lists the main components in the Microsoft. Practices.Prism.ViewModel namespace.

Microsoft.Practices.Prism.ViewModel Namespace

For more information about using the DataTemplateSelector class, see “MVVM QuickStart” in “Prism (Composite Application Guidance)” on MSDN (http://www.microsoft.com/prism).

Microsoft.Practices.Prism.Interactivity Namespace

The following table lists the main components in the Microsoft. Practices.Prism.Interactivity namespace.

Microsoft.Practices.Prism.Interactivity NamespaceMicrosoft.Practices.Prism.Interactivity Namespace

Microsoft.Practices.Prism.Interactivity. InteractionRequest Namespace

The following table lists the main components in the Microsoft. Practices.Prism.Interactivity.InteractionRequest namespace.

Microsoft.Practices.Prism.Interactivity. InteractionRequest NamespaceMicrosoft.Practices.Prism.Interactivity. InteractionRequest Namespace

For more information about interaction requests and displaying notifications, see “MVVM Advanced Scenarios” in “Prism (Composite Application Guidance)” on MSDN (http://www.microsoft.com/prism).

The URL to the bibliography can be found in the preface, in the final section, entitled, “Where to Go for More Information.”

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest News

Underlight As Accent, For Power and The Main Light for Photography

Underlighting, in which fill or accent light comes from under the topic, is not widely used technique in the traditional Portraits,...

How To Fix Overexposure As A Creative Tool, The Complete Guide

As an creative tool, overexposure is sort of underrated. What I’m close to propose could be a deliberate and well thought out technique for...

7D Mark II is Canon’s best DSLR cameras without full-frame sensor.

The expected long-awaited Canon EOS 7D Mark II are shipping in November for $ 1,799 without a lens. With a higher price tag, you...

Low key photography and How to isolate your subject.

Low key photography doesn’t depend on underexposure to make its point; the key to low key is that the majority of tones, even correctly...

High Key Lighting Techniques for Professional Photographers

I’ve written many times about high key lighting techniques and how to achieve them. The term “high key” is a bit misleading. As I’ve...

More Articles Like This

blograby facebook like page