Mvvm.Navigation.Uno.WinUI
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 HostApplicationBuilderExtensions. 2023-09-02 - feat: Removed Ioc.Default from main code. 2023-09-02 - feat: Added DI constructor generation for cases with ViewModel + Constructor. 2023-09-02 - feat: To single AddMvvmNavigation extension. 2023-09-02 - feat: Added HostBuilderExtensions generating. 2023-09-02 - feat: Added initial GlobalGenerator. 2023-09-02 - feat: Publish WebAssembly. 2023-09-02 - feat: Added ConstructorGenerator and ViewModelGenerator. 2023-09-02 - feat: Updated DP generator. 2023-09-02 - feat: Added AddViewsAndViewModels() extension when no classes with ViewFor attributes. 2023-09-02 🐞 Last 10 bug fixes: - fix: Fixed CI. 2023-09-02 - fix: Fixed CI. 2023-09-02 - fix: Fixed CI. 2023-09-02 - fix: Added some null checks. 2023-09-02 - fix: Fixed warnings. 2023-08-31
Install
dotnet add package Mvvm.Navigation.Uno.WinUI --version 0.1.0
Install-Package Mvvm.Navigation.Uno.WinUI -Version 0.1.0
<PackageReference Include="Mvvm.Navigation.Uno.WinUI" Version="0.1.0" />
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.