MvvmBindingPack.Debug 3.0.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package MvvmBindingPack.Debug --version 3.0.0                
NuGet\Install-Package MvvmBindingPack.Debug -Version 3.0.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="MvvmBindingPack.Debug" Version="3.0.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add MvvmBindingPack.Debug --version 3.0.0                
#r "nuget: MvvmBindingPack.Debug, 3.0.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 MvvmBindingPack.Debug as a Cake Addin
#addin nuget:?package=MvvmBindingPack.Debug&version=3.0.0

// Install MvvmBindingPack.Debug as a Cake Tool
#tool nuget:?package=MvvmBindingPack.Debug&version=3.0.0                

Model - View - ViewModel binding package.

Full details of package using link: MvvmBindingPack - Wiki

Version: 3.0.0

.Net Core App windows Desktop support

Dependences:

  • None

Version: 2.5.0

.Net Core transition version

Dependences:

  • None

(!) Breaking changes of IoC/DI container initialization.

Setup Unity DI container example for App.xaml.cs

    publicpartialclassApp : Application
    {

        privateUnityContainer _unityContainer;
        privateUnityServiceLocator _servicelocator;
        public App()
        {
            _unityContainer = newUnityContainer();
            _servicelocator = newUnityServiceLocator(_unityContainer);
            AutoWireVmDataContext.ServiceProvider = _servicelocator;
            var vmMw = newViewModelNew();
            // instance that will be resolved when it's used ServiceType
            _unityContainer.RegisterInstance(typeof(ViewModelNew),
            vmMw,newContainerControlledLifetimeManager());
        }
    }

Setup DotNet Core DI container example for App.xaml.cs

private void Application_Startup(object sender, StartupEventArgs e)
{

    ServiceCollection services = new ServiceCollection();
    services.AddSingleton<AutoBindingViewModel>();
    services.AddSingleton<IocBindingViewModel>();
    AutoWireVmDataContext.ServiceProvider = services.BuildServiceProvider();
}

Version: 2.0.1

Microsoft.Practices.ServiceLocation Support

Dependences: CommonServiceLocator (== 1.3.0) {namespace Microsoft.Practices.ServiceLocation}

Version: 2.0.1

Unity Container Support

Dependences: CommonServiceLocator (>= 2.0.2) {namespace CommonServiceLocator}

Recommended Unity Nuget Dependences: https://www.nuget.org/packages/Unity.Container (>= 5.8.6) https://www.nuget.org/packages/Unity.ServiceLocation (>= 2.1.1)

The decision to develop this binding package had been made in response of minimizing a the cost of the quality UI development along with using Agile development style. It is a big advantage to have a solution where you are able to refactor a dozen of Views and View Models, in a couple hours, by a customer request.

Welcome to MvvmBindingPack

MvvmBindingPack is the robust MVVM framework platform for UX high-quality solutions with support of IoC/DI containers. MVVM pattern is widely used in developing of XAML-based GUI applications. It is impossible to provide the quality UX design implementations without using this pattern. Quality of UX design directly depends on the techniques or features that used for implementing the MVVM pattern. Clear separation of concerns between View (XAML code coupled with its code-behind) and View Model characterizes a profession level and quality and the of the product implementation. The package has the compatible features implementation for XAML WPF and Win Store Application XAML. MVVM pattern in UI development process looks like a principal of "Dependency Inversion" between View and View Model.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp3.0 is compatible.  netcoreapp3.1 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETCoreApp 3.0

    • No dependencies.

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
8.0.0 73 11/20/2024
6.0.0 471 11/14/2021
5.0.0 449 1/1/2021
3.1.0 579 12/8/2019
3.0.0 589 10/13/2019
2.5.0 548 10/13/2019
2.0.1 1,009 1/9/2018
1.9.0 951 7/30/2017
1.8.5.1 1,019 6/26/2016
1.8.2.3 977 4/2/2016

Release: netcoreapp3.0 Windows WPF Only; Signed Assembly;
     Breaking changes(!):
     Initialize DI/IoC:
     MvvmBindingPack.AutoWireViewConrols.ServiceProvider static property with “Microsoft.Extensions.DependencyInjection” ServiceProvider.