Magellan Navigator

Why did you decide to write your own Navigator class instead of using the built-in NavigationService class provided as part of the Windows.System.Navigation namespace? Was it for the reasons you outlined in your Magellean and WPF Page Management Woes article?

One advantage to using the built-in NavigationService class is the support for simple navigation using the Hyperlink element. Does Magellan support the Hyperlink element? Most of your examples use Button elements to control navigation instead. As a web guy, I find hyperlinking a more natural concept for moving around.

Hi Dean,

The issue with the built in NavigationService is you can only navigate to a .XAML page. That doesn't give a chance for the controller to intercept to decide which page to show.

However, you can use the Click event of the Hyperlink to navigate, or use the NavigateAction/NavigateBehavior to perform the navigation.

Paul

Ah. That makes sense. The built-in NavigationService simply links one View (or .XAML page) to another directly.

That also explains why other MVC/MVP/MVVM frameworks avoid using the built-in service, too.

I dont't understand that with the built-in NavigationService I can only navigate to a .XAML page.

Isn't ist possible to navigate to a viewmodel class like this

_mainFrame.NavigationService.Navigate(new MyViewModel());

and define a Datatemplate for it? (and that Datatemplate could be a Page)