ClinicalOffice.MvvmTools.WPF 1.2.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package ClinicalOffice.MvvmTools.WPF --version 1.2.0
NuGet\Install-Package ClinicalOffice.MvvmTools.WPF -Version 1.2.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="ClinicalOffice.MvvmTools.WPF" Version="1.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add ClinicalOffice.MvvmTools.WPF --version 1.2.0
#r "nuget: ClinicalOffice.MvvmTools.WPF, 1.2.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install ClinicalOffice.MvvmTools.WPF as a Cake Addin
#addin nuget:?package=ClinicalOffice.MvvmTools.WPF&version=1.2.0

// Install ClinicalOffice.MvvmTools.WPF as a Cake Tool
#tool nuget:?package=ClinicalOffice.MvvmTools.WPF&version=1.2.0

A library to enable direct binding of events in your views and methods in the view models, also provide easy way of creating commands and commands collection.

Product Compatible and additional computed target framework versions.
.NET Framework net461 is compatible.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.3.0 665 5/1/2019
1.2.0 577 4/24/2019
1.1.1 529 4/10/2019
1.1.0 528 4/10/2019
1.0.1 559 3/30/2019
1.0.0 547 3/29/2019

-Bug fix: WPF buttons does not catch command CanExecuteChanged.
     
-Added: changed event binding behaviour when using element name (you don't have to add DataContext to access underlaying ViewModel) PLEASE READ WIKI FOR THIS.