May 26, 2009 at 7:31 PM
Edited May 26, 2009 at 7:32 PM
I will try to provide answers to your questions separately.
The Navigation from SL 3 and
UI Composition from Prism-v2 “systems” are independent.
I will not explain a lot about SL3 navigation, since I am no expert in such topic but will provide some links that might be useful:
Silverlight 3: Navigation URI Routing
A guide to Silverlight 3 new features
NAVIGATION FRAMEWORK (video)
Have in mind that Prism-v2 does not specifically target navigation (neither in
WPF nor Silverlight), and it was released before the Silverlight 3 Beta release. I will explain how regions and Views are used in Prism-v2.
UI Composition consists in composing the user interface with views from different modules. To configure the UI’s layout, placeholders for
views (named Regions in Prism) are used. At runtime, regions are populated with views to compose the UI. Although the concepts of Frame and Region could sound similar, and Navigation could be implemented using Regions, they serve different purposes as
navigation is meant to ease transition between views.
Silverlight 3 Navigation can be used with Prism-v2, but with some limitations. Mariano Converti and I have tried it, so you can read about that
in the following links:
How To: Integrate a Prism
v2 application with the Silverlight 3 Navigation Framework
Prism 2 & Silverlight 3 Beta Navigation
The following links might be useful to better understand UI Composition:
Shell and View
How to: Add a Region
How to: Show a View in a Region Using View Discovery UI Composition
How to: Show a View in a Region Using View Injection UI Composition
About Prism v-Next
The following post has some information about future versions of Prism:
by David Hill (p&p Architect)
Quote from that post:
“We're planning the next release of Prism which will target Silverlight 3.0 (and WPF 4.0)…”
Please let me know if this helps.