Mvvm.Navigation.Uwp 1.2.6

Mvvm.Navigation

Provides platform independent navigation at the MVVM level and a Source Generator that automatically binds view and view models and registers this in your DI container.

🔥Features🔥

• Uses DI to resolve your view from view model.
• Generates an extension method for you with all your Views and ViewModels to register them in DI.
• Does not contain custom controls, everything happens based on the attached dependency property and does not limit the user.
• Allows forward/backward navigation like in Chrome.
• Allows you to receive activation/deactivation events - just implement IActivatableViewModel for your ViewModel.
• Allows you to generate a typed ViewModel property via an attribute, bound to your BindingContext and initialized from DI.
• Supports automatic mapping between View and ViewModel based on a global attribute.
• Allows case-by-case, attribute-based control for Views.

Usage

1. Add .AddMvvmNavigation() call to your Host builder or IServiceCollection:

public sealed partial class App
{
    public App()
    {
        AppHost = Host
            .CreateDefaultBuilder()
            .AddMvvmNavigation()
            .Build();
    }
}

2. Add ViewFor attribute to your views:

using Mvvm.Navigation;

[ViewFor<MainViewModel>]
public partial class MainPage : UserControl;

or assembly level attribute(nameof behavior is ignored and the full namespace is taken):

[assembly:MapViews(
    viewsNamespace: nameof(MyNamespace.Views),
    viewModelsNamespace: nameof(MyNamespace.ViewModels))]

3. Add Navigator to your ViewModel:

public Navigator<ObservableObject> Navigator { get; }

4. Add commands to your views(or just use Navigator from ViewModel):

<Grid>
    <Button
        Command="{Binding Navigator.NavigateByTypeCommand}"
        CommandParameter="{x:Type viewModels:BlueViewModel}"
        />
    <ContentControl mvvm:Properties.Navigator="{Binding Navigator}"/>
</Grid>

Tip: you can use CommandParameter="{mvvm:Type Type=viewModels:BlueViewModel}" for WinUI/UWP/Uno platforms.

Base

The library was written as a replacement for ReactiveUI in a real project, and inherits some concepts from it, excluding reactivity.
If you have the same task, then the changes are as follows:

• Replace RoutingState with Navigator
• Replace IScreen with INavigable
• Replace ReactiveUserControl with UserControl
• Replace ReactiveWindow with Window
• Replace RoutedViewHost and ViewModelViewHost with ContentControl
• Use mvvm:Properties.ViewModel and mvvm:Properties.Resolver/mvvm:Properties.Navigator(includes resolver) attached dependency properties.

Support

Priority place for bugs: https://github.com/HavenDV/Mvvm.Navigation/issues
Priority place for ideas and general questions: https://github.com/HavenDV/Mvvm.Navigation/discussions
I also have a Discord support channel:
https://discord.gg/g8u2t9dKgE