This is a small set of examples on how to navigate the UI in WPF. This is still work in progress - just a repo to dump some thoughts and experiences.

The idea is to try and not use any 3rd party libraries. This project has been written using Jetbrains Rider.

Uses simple code behind in the window to navigate pages within a frame.

Uses simple code behind in the window to navigate pages outside of the application within a frame.

Introduces a simple PageNavigationService to navigate between views within a frame.

This is work in progress. The purpose is to navigate to named routes in the wpf application as opposed to Uris. The api for this has currently been developed in the wpf-tdd project

This project came about from the above. Given the turnaround time of stop starting the application to write a navigation service off the top of my head where I had never done one before seemed pointless.

Therefore this project is geared up for Named Route and Uri navigation.

So this project uses a combination of:

• Xunit.StaFact - allows running of WPF resources in tests
• Autofac - uses the DI to new up new pages and view models when the view and view model is resolved

The concept diagram can be found in the wiki.

The design was driven from initial thought and TDD. Checkout:

• NavigatingNamedRoutesTdd.cs
• NavigatingUriRoutesTdd.cs

This can be done by:

var views = new Views();
views.Register<Page2WithVm, Page2Vm>((view, dataContext) => view.DataContext = dataContext);
views.RegisterForAutoDataContext<Page3WithVm, Page3Vm>();

This allows DI to kick in and create both the view and view model. This only works for named routes. The RouteNavigationService kicks in and tells the then set the NavigationController to set the Content.

NavigationController navigationController = new(() => _context.mainWindow.NavigationHost.NavigationService);

We add routes simply by:

var routes = new Routes();
routes.Add(new("Page1", typeof(Page1)));

Then to navigate to a page:

_routeNavigationService.NavigateTo(Named("Page3"));