Mvvm.Navigation.Uno
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: 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 - fix: Fixed "An expression is too long or complex to compile" in big projects. 2023-09-07 - fix: Fixed MAUI bug without ViewFor attributes. 2023-09-05 - fix: Now Navigator is transient by default 2023-09-04
Install
dotnet add package Mvvm.Navigation.Uno --version 1.2.4
Install-Package Mvvm.Navigation.Uno -Version 1.2.4
<PackageReference Include="Mvvm.Navigation.Uno" Version="1.2.4" />
Frameworks
Dependencies
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
NuGet marks this package as deprecated. Review the publisher's migration guidance before adopting it.
Compatibility metadata lists 5 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.