Post the new of release of nRoute, I've updated and upgraded seven sample applications from earlier releases to the latest version.
1. Future Desktop 2 [Silverlight 4, nRoute.Framework]
Future Desktop was the first ever demo-app for nRoute in Silverlight 2, and since then we've come a long way - as a metric for progress consider in upgrading to the latest release of nRoute we've managed to cut the code count by half. Also, I could sense two non-quantifiable improvements, 
one nRoute is a lot less invasive as it generally stays out by the way of attributes. Secondly within Views, use of Blend based behaviors is a lot more productive than having to fiddle with xaml directly.
As can be seen on the right, I've added bit of the UI functionality - basically, now you can add, close, and refresh workspaces. However, I've removed the browser-shell integration functionality, which allowed you to navigate back or forward directly from the browser's shell - I did this because nRoute is now using Silverlight's built-in Browser History Manager which unfortunately can't tell when one navigates' back. Also there are some new keyboard shortcuts for managing workspaces.
Read more about the Future Desktop app
View the nRoute's Future Desktop 2 App here [Silverlight 4, nRoute.Framework]
2. Office(r) 2010 [Silverlight 4, nRoute.Framework]
This demo mimics Office 2010 beta version's look and feel, and it was primarily designed to showcase nRoute's navigation feature-set and use of containers-within-containers. Changes from the earlier version include use of Site-Maps, Controllers and View-Services for things like the message-toasts. Also in the earlier version we made of us TransitioningContent Control from Silverlight Toolkit to show navigation-transition effects, this has been replaced to use the newly added Transition Effects feature in Silverlight/Blend 4:
Making use of navigating-related transition-effects in your app is quite easy, it's actually just three steps - one, edit (or create a new) template for your navigation container, two, add a Navigating-to-Navigated transition (shown with the green rectangle border), and three, pick and choose your transition effect (using the fx button shown with a red circle border). Also shown above are some of the built-in effects from which I've used the Wipe Effect, but you could always add your custom effects.
Read more about the Officer 2010 app
View the Office(r) 2010 v2 App here [Silverlight 4, nRoute.Framework]
3. Web Xcel [Silverlight 4, nRoute.Toolkit Sample]
The Web Xcel sample was designed to showcase the use of ViewServices - which basically are services that are implemented visually. So things like toasts, open/save file dialogs, confirmation dialogs, etc. Also, I've updated the sample to show how you can implement ViewServices from your ViewModel in addition to doing it via code-behinds and using custom-controls.
Read more about the Web Xcel app
View the WebXcel App here [Requires Silverlight 4]
4. Office(r) Xcel [Silverlight 4, nRoute.Framework Sample]
This sample is basically an amalgamation of the previous two samples, the backstage view allows you to open-close ".xcel" files and the spreadsheet-like view visualizes the content.
Read more about the Office(r) Xcel App
View the Office(r) Xcel App here [Silverlight 4, nRoute.Framework]
5. Silverlight Console [Silverlight 4, uses nRoute.Toolkit]
The Silverlight Console project makes use of nRoute to provide two things, one a Console Window control that can be used to output text and take input, and two, it provides a script-commands engine that can dynamically resolve, parse, and execute script based commands. You combine the two and you have a domain specific console control and runtime right within your app.
To coordinate with samples release, I've just updated Silverlight Console to Silverlight 4, and as a way of samples included some new script-commands that can list, start and stop processes on the host server right from the textual interface.
Read Silverlight Console's introduction here
Get the source and sample app from Codeplex
6. Sudoku X2 : iPhone & WP7 [Silverlight, uses nRoute.Toolkit]
The Sudoku sample is an end-to-end example of a MVVM style application - it shows how we can break apart an application in a Model, View, and ViewModel components only to bring it back as a loosely-coupled but highly cohesive application using nRoute. Using the clearly demarcated setup, I've refactored the sample to support two UIs (iPhone and WP7 themed) using the same View, ViewModel, ViewServices and other non-visual components. In addition to the main-view visuals, the working/busy indicator controls for WP7 has also been updated to use running bars - though both operate using the same ViewService definition.
Read more about the Sudoku MVVM app
View both Sudoku UIs side-by-side here
7. Simple MVVM [WPF, Silverlight 4, and Windows Phone 7, uses nRoute.Framework]
I've also updated the Simple MVVM sample that shows without much fanfare how to use Navigation, Navigation-State, ViewModels, Services, etc across Silverlight, WPF and Windows Phone 7. Now, I've updated the sample to first make use of SiteMaps to define a crude navigation-menu shown in the UI, and secondly to seamlessly load and use external resources again just by just declaring it in the SiteMap. The SiteMap for the WPF version is shown below:
The SiteArea section defines an external resource which is uniquely identified using a SiteArea key ("ExtendedArea" above), and we use the same key to indicate that a Navigation page in the SiteMap resides in an external resource. Now, when asked for the externally resident Navigation page, nRoute automatically downloads, loads, maps and initializes all included resources (including things like Services, ViewModels, ViewServices, Navigation-resources etc), following which it resolves the asked for Navigation page. In the Silverlight version of the sample, we make use of an Xap file (though you could use a dll), whereas for WP7 loading of external resources at runtime is not allowed so we've just referenced the resource but it still is provisioned in a loosely-coupled manner like in Silverlight and WPF.
Future Reference App
For future release I'm working on a reference LOB application for nRoute that will provide a much broader and in-depth look at how you can leverage nRoute to make a composite application including the use of MVVM related techniques. And in my experience nRoute really shines in that composite role, as it allows you compose at various levels of consumption - at the application-level using things like SiteAreas, Modules, Services etc., at the infrastructure-level using Navigation, Messaging-Channels, IoC etc. and at the UI-level using ViewModels, ViewServices, ICommands, Behaviors etc. With the larger point being that by breaking you application into properly separated components there is a lot of synergy to be had in bringing it together using nRoute - and that's what I intend to demonstrate.
Download all the Samples Apps' Source-Code from Codeplex