Dreamine.MVVM.FullKit

All-in-One package set for building WPF MVVM applications with the Dreamine architecture.

Dreamine.MVVM.FullKit is a meta-package/repository concept that brings together the core Dreamine MVVM modules used for WPF applications: DI, ViewModel infrastructure, source generators, locator wiring, WPF runtime integration, behaviors, extensions, and optional hybrid hosting.

➡️ 한국어 문서 보기

---

Overview

Dreamine.MVVM.FullKit is designed for developers who want a lightweight but explicit MVVM stack for WPF.

This kit brings together:

• Dreamine.MVVM.Core
  Core container and runtime infrastructure centered on DMContainer.

• Dreamine.MVVM.Interfaces
  Shared contracts for navigation, resolver abstraction, event base patterns, and MVVM interaction boundaries.

• Dreamine.MVVM.ViewModels
  Base ViewModel types and fundamental MVVM runtime support.

• Dreamine.MVVM.Attributes
  Declarative attributes such as DreamineProperty and command-related attributes used by generators.

• Dreamine.MVVM.Generators
  Roslyn source generators that reduce boilerplate by generating MVVM code automatically.

• Dreamine.MVVM.Locators
  Naming-convention and resolver-based View ↔ ViewModel connection infrastructure.

• Dreamine.MVVM.Locators.Wpf
  WPF-specific auto-wiring support such as DataContext connection and binder integration.

• Dreamine.MVVM.Wpf
  WPF runtime bootstrap layer centered on DreamineAppBuilder.

• Dreamine.MVVM.Behaviors.Core
  Base behavior abstraction infrastructure.

• Dreamine.MVVM.Behaviors.Wpf
  WPF behavior execution/runtime layer.

• Dreamine.MVVM.Behaviors
  Ready-to-use MVVM-friendly behaviors such as EnterKey and focus helpers.

• Dreamine.MVVM.Extensions
  Utility helpers and extension points used across Dreamine MVVM applications.

• Dreamine.Hybrid / Dreamine.Hybrid.Wpf / Dreamine.Hybrid.BlazorApp
  Optional hybrid hosting stack for embedding Blazor UI inside WPF.

---

Why FullKit exists

Many MVVM projects become fragmented because infrastructure, generator setup, locator rules, and WPF runtime glue are introduced independently.

Dreamine.MVVM.FullKit exists to provide a unified starting point with these goals:

• reduce startup complexity
• keep architecture explicit
• separate platform-neutral and platform-specific responsibilities
• support testable, DI-friendly ViewModel design
• remove repetitive MVVM boilerplate through source generation
• keep WPF runtime concerns out of platform-neutral packages

---

Architecture Summary

graph LR
    Core[Dreamine.MVVM.Core] --> Interfaces[Dreamine.MVVM.Interfaces]
    Core --> ViewModels[Dreamine.MVVM.ViewModels]
    Core --> Locators[Dreamine.MVVM.Locators]
    Locators --> LocatorsWpf[Dreamine.MVVM.Locators.Wpf]
    Core --> Wpf[Dreamine.MVVM.Wpf]
    Core --> Extensions[Dreamine.MVVM.Extensions]
    Core --> BehaviorsCore[Dreamine.MVVM.Behaviors.Core]
    BehaviorsCore --> BehaviorsWpf[Dreamine.MVVM.Behaviors.Wpf]
    BehaviorsWpf --> Behaviors[Dreamine.MVVM.Behaviors]
    Core --> Attributes[Dreamine.MVVM.Attributes]
    Attributes --> Generators[Dreamine.MVVM.Generators]
    Core --> Hybrid[Dreamine.Hybrid]
    Hybrid --> HybridWpf[Dreamine.Hybrid.Wpf]
    HybridWpf --> HybridBlazor[Dreamine.Hybrid.BlazorApp]

Loading

---

Main Features

1. Lightweight DI container

DMContainer provides the lightweight registration and resolution model used by Dreamine.

Typical use cases:

• singleton registration
• factory-based registration
• constructor injection
• explicit runtime ownership

This keeps the container simple and predictable for WPF applications.

2. Source-generated MVVM boilerplate

Dreamine reduces repetitive code by combining:

• attributes
• Roslyn source generators
• generated property notification code
• generated command wiring

This allows ViewModels to stay focused on state and behavior instead of plumbing.

3. Convention-based ViewModel resolution

Dreamine uses View ↔ ViewModel mapping conventions with extension points for custom resolvers.

Typical pattern:

• Views.MainWindow → ViewModels.MainWindowViewModel
• explicit registration when convention is not enough
• optional automatic DataContext assignment in WPF

4. WPF runtime bootstrap

DreamineAppBuilder is the WPF bootstrap entry point.

It is responsible for:

• initializing Dreamine runtime for WPF
• registering View ↔ ViewModel mappings
• auto-registering types into DMContainer
• attaching DataContext at runtime when configured

5. WPF Behaviors

Dreamine behaviors help keep interaction logic out of code-behind.

Examples:

• Enter key → command execution
• focus on load
• drag behaviors
• attached interaction helpers

6. Optional WPF + Blazor hybrid hosting

For applications that need a hybrid UI model, Dreamine provides:

• WPF hosting control
• Blazor root component hosting
• service wiring
• message bus style integration between shell and hosted UI

---

Recommended Package Composition

A typical WPF project may use this composition:

<ItemGroup>
  <PackageReference Include="Dreamine.MVVM.Core" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Interfaces" Version="*" />
  <PackageReference Include="Dreamine.MVVM.ViewModels" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Attributes" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Generators" Version="*" OutputItemType="Analyzer" ReferenceOutputAssembly="false" />
  <PackageReference Include="Dreamine.MVVM.Locators" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Locators.Wpf" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Wpf" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Behaviors" Version="*" />
  <PackageReference Include="Dreamine.MVVM.Extensions" Version="*" />
</ItemGroup>

For hybrid hosting:

<ItemGroup>
  <PackageReference Include="Dreamine.Hybrid" Version="*" />
  <PackageReference Include="Dreamine.Hybrid.Wpf" Version="*" />
  <PackageReference Include="Dreamine.Hybrid.BlazorApp" Version="*" />
</ItemGroup>

---

Quick Start

1. Initialize WPF runtime

In App.xaml.cs:

using System.Reflection;
using System.Windows;
using Dreamine.MVVM.Wpf;

namespace SampleApp;

/// <summary>
/// Application bootstrap.
/// </summary>
public partial class App : Application
{
    /// <summary>
    /// Handles application startup.
    /// </summary>
    protected override void OnStartup(StartupEventArgs e)
    {
        base.OnStartup(e);

        DreamineAppBuilder.Initialize(Assembly.GetExecutingAssembly());
    }
}

2. Create a ViewModel

using Dreamine.MVVM.Attributes;
using Dreamine.MVVM.ViewModels;

namespace SampleApp.ViewModels;

/// <summary>
/// Main window ViewModel.
/// </summary>
public partial class MainWindowViewModel : ViewModelBase
{
    [DreamineProperty]
    private string _title = "Dreamine FullKit";

    [RelayCommand]
    private void ChangeTitle()
    {
        Title = "Updated";
    }
}

3. Bind View to ViewModel automatically

<Window x:Class="SampleApp.Views.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:locator="clr-namespace:Dreamine.MVVM.Locators.Wpf;assembly=Dreamine.MVVM.Locators.Wpf"
        locator:ViewModelBinder.AutoWireViewModel="True">
    <Grid>
        <StackPanel>
            <TextBlock Text="{Binding Title}" />
            <Button Content="Change"
                    Command="{Binding ChangeTitleCommand}" />
        </StackPanel>
    </Grid>
</Window>

---

When to use FullKit

Use FullKit when:

• you want a consistent Dreamine-based WPF MVVM starting point
• you want explicit architecture instead of hidden framework magic
• you want generator-based productivity without a heavy runtime
• you want clear separation between platform-neutral and WPF-specific layers
• you want optional hybrid expansion later

Do not use FullKit as a blind dependency bundle. Select only the modules that your application actually needs.

---

Responsibility Boundaries

Recommended boundaries:

• Core: container and fundamental infrastructure
• Interfaces: contracts only
• ViewModels: UI state and interaction logic
• Locators: View ↔ ViewModel connection rules
• Wpf: runtime bootstrap and WPF-specific binding glue
• Behaviors: reusable UI interaction units
• Hybrid: WPF + Blazor integration only when needed

This separation keeps lower layers independent from upper layers.

---

Suggested Repository Layout

Dreamine.MVVM.FullKit/
├─ README.md
├─ README_KO.md
├─ LICENSE
├─ src/
│  ├─ Dreamine.MVVM.Core/
│  ├─ Dreamine.MVVM.Interfaces/
│  ├─ Dreamine.MVVM.ViewModels/
│  ├─ Dreamine.MVVM.Attributes/
│  ├─ Dreamine.MVVM.Generators/
│  ├─ Dreamine.MVVM.Locators/
│  ├─ Dreamine.MVVM.Locators.Wpf/
│  ├─ Dreamine.MVVM.Wpf/
│  ├─ Dreamine.MVVM.Behaviors.Core/
│  ├─ Dreamine.MVVM.Behaviors.Wpf/
│  ├─ Dreamine.MVVM.Behaviors/
│  ├─ Dreamine.MVVM.Extensions/
│  ├─ Dreamine.Hybrid/
│  ├─ Dreamine.Hybrid.Wpf/
│  └─ Dreamine.Hybrid.BlazorApp/
└─ samples/

---

License

MIT License

---

Notes

This README is a synthesized FullKit-level document built from the current Dreamine repositories and their package-level documentation so that the FullKit repository can expose a unified entry document.