Following our last post, we now have a solid framework for our app to handle state and lifecycle. However, at this point we are still navigating the app directly from the code-behind of the Views, which ties the navigation to the platform code. In addition to not cluttering up our code, this also restricts us from fully taking advantage of the cross-platform opportunities offered by MvvmLight.
Today we’ll see how to centralize this navigation code, removing the platform-specific definition and moving from the code-behind to the ViewModels, allowing maximum reuse of code. We’ll begin with the code related to navigation.
Read more on the Falafel Software Blogs: Windows 10 Development: MvvmLight NavigationService and the Behaviors SDK
Latest posts by selaromdotnet (see all)
- Xamarin Forms: Public C# Properties Missing on Android - June 19, 2017
- Quick Fix: Unwanted Rounding When String Formatting Number as Currency - June 8, 2017
- Windows 10 Development: Custom StateTriggers - October 1, 2015