MvvmCross is the .NET MVVM framework for cross-platform solutions, including Xamarin iOS, Xamarin Android, Xamarin Forms, Windows and Mac.
This package contains the 'Visibility' plugin for MvvmCross
<hr />
<h4 align="center">
Check out the <a href="https://www.mvvmcross.com/documentation">MvvmCross docs</a>
</h4>
<hr />
👀 Check out mvvmcross.com to get started with MvvmCross 👀
MvvmCross is a opinionated cross-platform MVVM framework. It enables developers to create apps using the MVVM pattern in the .NET ecosystem. We support Android, iOS, MacCatalyst, TvOS, macOS, WinUI, WPF. Using MvvmCross allows for better code sharing by allowing you to share behavior and business logic between platforms.
Among the features MvvmCross provides are:
ViewModel to View bindings using own customizable binding engine, which allows you to create own binding definitions for own custom views
ViewModel to ViewModel navigation, helps you share behavior on how and when to navigate
Inversion of Control through Dependency Injection and Property Injection
Plugin framework, which lets you plug-in cool stuff like GPS Location, Localization, Sensors, Binding Extensions and a huge selection of 3rd party community plug-ins
MvvmCross is extendable by you. We strive to let as much code be configurable and overridable, to let the developer decide how they want to use the framework. However, the framework is very usable without doing anything.
Installation
Grab the latest MvvmCross NuGet package and install in your solution.
Install-Package MvvmCross
Make sure that both the shared core project and your application projects include the NuGet. For more details please visit the Getting Started documentation, which also provides easier ways, through Visual Studio and Xamarin Studio plugins to install and manage MvvmCross in your project.
Filing issues
We want to keep the GitHub issues list for bugs, features and other important project management tasks only. If you have questions please see the Questions & support section below.
When filing issues, please select the appropriate issue template. The best way to get your bug fixed is to be as detailed as you can be about the problem.
Providing a minimal git repository with a project showing how to reproduce the problem is ideal. Here are a couple of questions you can answer before filing a bug.
MonoCross was the original starting point for this project, and was used as a reference under MIT
Tiny bits of MvvmLight are redistributed and modified under MIT
Messenger ideas from JonathanPeppers/XPlatUtils under Apache License Version 2.0, and from GrumpyDev/TinyMessenger under simple license of "THIS CODE AND INFORMATION IS PROVIDED "AS IS" WITHOUT WARRANTY"
