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
⭐ Last 10 features:
- feat: Added BeforeInitializeComponent/AfterInitializeComponent partial methods when generating constructors. Fixed ViewModel init order. 2023-09-14
- feat: Now you can implement IActivatable for window/control and it will work. 2023-09-14
- feat: Implemented assembly:MapViews attribute. 2023-09-05
- feat: Added Activation support. 2023-09-04
- feat: Added separate property for InitializeComponent constructor. 2023-09-03
- feat: Released 0.2.0. 2023-09-03
- feat: Added Type markup extension. 2023-09-03
- feat: Added Properties.ViewModelType. 2023-09-02
- feat: Added HostApplicationBuilderExtensions. 2023-09-02
- feat: Removed Ioc.Default from main code. 2023-09-02
🐞 Last 10 bug fixes:
- fix: Fixed work of ServiceLifetime.None. 2023-09-22
- fix: Fixed ViewLifetime/ViewModelLifetime. 2023-09-22
- fix: Fixed ViewModel/ViewModelType default binding mode. 2023-09-22
- fix: Removed views with ViewFor attribute from MapViews generation. Closes #6. 2023-09-17
- fix: Fixed issue with combined MapViews and ViewFor. 2023-09-16
- fix: Added try to resolve IResolver from Ioc.Default. 2023-09-15
- fix: Fixed ambiguities with resolver. 2023-09-14
- fix: Generated ViewModel property can be null now. 2023-09-12
- fix: Fixed problems with DependencyPropertyGenerator. 2023-09-11
- fix: Fixed "An expression is too long or complex to compile" in big projects. 2023-09-07
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
Add .AddMvvmNavigation() call to your Host builder or IServiceCollection:
public sealed partial class App
{
public App()
{
AppHost = Host
.CreateDefaultBuilder()
.AddMvvmNavigation()
.Build();
}
}
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):
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.
