Search

The following changes were implemented in this release:

• All Visual Studio projects (Composite Application Library, reference implementation, and Quickstarts) were migrated to use Silverlight 3. If you do not want to upgrade to Silverlight 3, see Opening Projects with Silverlight 2.
• TabRegionControlAdapter was modified to support binding in the TabItem’s control header in Silverlight 3. This feature was present for Silverlight 2 but stopped working in Silverlight 3 due to a breaking change. It now supports both versions of Silverlight. [...]

In this article Jeremy Likness demonstrates how to build decoupled ChildWindow dialogs using Prism.

A common user interface component is the confirmation or message box, which is often presented as a dialog returns a boolean (OK/Cancel). There are a variety of ways to achieve this, but how can you decouple the implementation of the popup from the request itself? This is necessary, for example, for unit testing when you may not have a UI available. This article demonstrates one solution using Silverlight and the Composite Application Guidance library, also known as Prism.

In this post Damian Schenkelman compares the validation provided by the RI to the one that comes with Silverlight 3.

I came up to the conclusion that the approach provided by p&p is pretty similar to one of the approaches Silverlight 3 allows related to validation. You can watch this video about Silverlight 3 Validation which explains some of the possibilities you have.

After that I decided to replace the RI’s validation using Silverlight 3 and was able to do it with some minor changes (you can check the OrdersDetailsView and OrdersDetailsPresentationModel which have most of the changes).

Adam Kinney announced that Composite Application Guidance, also known as Prism, version 2 has been released.