Similar conventions exist for various common controls: It probably saved me the most work and is the most fun to work with.īutton with x:Name="Start” automatically binds to void Start() in the attached viewmodel (which itself is automatically resolved by name as well).Īdditionally the button can also bind to bool CanStart which will determine the enabled state of the button. From the integrated IoC container, auto-bindings for view-viewmodels to the platform-independent abstractions (navigation, storage, view activations and deactivations).īut my favorite feature is the convention-based bindings which works based on the control names. Like any other MVVM framework it makes working with XAML a lot easier. I’d like to feature the framework because I have been using it for years for various WPF as well as Windowsphone applications and it has saved me probably hundreds of hours. With strong support for MVVM and other proven UI patterns, Caliburn.Micro will enable you to build your solution quickly, without the need to sacrifice code quality or testability.
Caliburn.Micro is a small, yet powerful framework, designed for building applications across all XAML platforms.
0 kommentar(er)
