Meteion.Toolkit.WPF.Dialogs 1.8.0

dotnet add package Meteion.Toolkit.WPF.Dialogs --version 1.8.0
                    
NuGet\Install-Package Meteion.Toolkit.WPF.Dialogs -Version 1.8.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="Meteion.Toolkit.WPF.Dialogs" Version="1.8.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Meteion.Toolkit.WPF.Dialogs" Version="1.8.0" />
                    
Directory.Packages.props
<PackageReference Include="Meteion.Toolkit.WPF.Dialogs" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Meteion.Toolkit.WPF.Dialogs --version 1.8.0
                    
#r "nuget: Meteion.Toolkit.WPF.Dialogs, 1.8.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.
#:package Meteion.Toolkit.WPF.Dialogs@1.8.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Meteion.Toolkit.WPF.Dialogs&version=1.8.0
                    
Install as a Cake Addin
#tool nuget:?package=Meteion.Toolkit.WPF.Dialogs&version=1.8.0
                    
Install as a Cake Tool

Meteion Toolkit

A toolkit for accellerating .NET development, especially for localized and MVVM applications.

Why?

I am tired of writing the same code to do the same thing between applications and I'm sure you are too. Libraries such as CommunityToolkit.MVVM help, but they don't provide enough.

PRISM is confusing and complex, and doesn't feel natural (in my opinion) with dependency injection. Maybe that's a user error, but the methods used in the toolkit feel better to me.

Packages

Package NuGet Downloads
Meteion.Toolkit.WPF NuGet Downloads
Meteion.Toolkit.WPF.MVVM NuGet Downloads
Meteion.Toolkit.MVVM NuGet Downloads
Meteion.Toolkit.Abstractions NuGet Downloads
Meteion.Toolkit.WPF.Hosting NuGet Downloads
Meteion.Toolkit.WPF.SplashScreen NuGet Downloads
Meteion.Toolkit.WPF.Dialogs NuGet Downloads
Meteion.Toolkit.Dialogs.Abstractions NuGet Downloads
Meteion.Toolkit.WPF.Localization NuGet Downloads
Meteion.Toolkit.Localization.Abstractions NuGet Downloads
Meteion.Toolkit.Localization.Check NuGet Downloads
Meteion.Toolkit.Localization.Check.Core NuGet Downloads
Meteion.Toolkit.Localization.KeysGenerator NuGet Downloads
Meteion.Toolkit.WPF.MarkdownViewer NuGet Downloads
Meteion.Toolkit.WPF.MarkdownViewer.Renderers.HTML NuGet Downloads

Getting started

New here? Getting started builds a small navigation app step by step. Two short pages explain the ideas behind it: Scoping (each window gets its own services) and Page vs window resolution (showing a view model as a page or as a window).

Templates

dotnet new templates for a RESX file, a WPF application, and a WPF application with localization:

dotnet new install Meteion.Toolkit.Templates
dotnet new meteion-wpf -n MyApp

See Templates for the full list, local install from this repository, and what they generate.

Features

MVVM and Navigation Helpers

Requires: Meteion.Toolkit.MVVM

It's best used in tandem with CommunityToolkit.Mvvm, but it can be used standalone as well.

  • Navigation Loading Indicator: Opt-in events (INavigationProgress) for showing a spinner (via StatefulContainer) during slow navigations, with built-in flicker protection. See Navigation Loading Indicator.
  • ViewState / IStatefulViewModel: One MVVM state object that feeds StatefulContainer. See StatefulContainer.
  • INavigationAwareViewModel / IAsyncNavigationAwareViewModel - Interfaces for view models that want to be notified when they are navigated to or from.

Mostly, it just supports you creating ViewModels and Views that can be navigated to, and provides a way to show a loading indicator during slow navigations.

WPF

Controls
  • StatefulContainer: A control for showing a loading indicator, your content, or an error state (with optional Retry), with overridable templates and a Replace or Overlay mode. Drive it from any state object, or use ViewState/IStatefulViewModel from the MVVM package. See StatefulContainer.
  • PlaceholderContainer: A control that hides its content and shows a placeholder template when a bound value is null or empty. Use it for "no items" lists and "nothing selected" panes. It updates live with ObservableCollection. See PlaceholderContainer.
MarkdownViewer

Requires: Meteion.Toolkit.WPF.MarkdownViewer (and optionally Meteion.Toolkit.WPF.MarkdownViewer.Renderers.HTML)

MarkdownViewer renders markdown as real WPF elements: headings, lists, task lists, tables, code blocks with a Copy button, links and images. It follows your theme (including dark mode), re-renders live as the text or the app's culture changes, and is locked down by default (links open only for http, https and mailto; images load only from the app's directory). Add the HTML renderer to draw raw HTML in markdown, restyle everything through resource keys, and extend it with your own renderers and syntax. See MarkdownViewer.

<mtk:MarkdownViewer Markdown="{Binding Notes}" />
GenericHost Hosting

Requires: Meteion.Toolkit.WPF.Hosting

Integrates with .NET Generic Host for dependency injection and configuration in your WPF applications: ConfigureLaunchWindow<T>(), ConfigureApplication<TApp>() and BuildWpfHost() set up and run the app, and your App derives from WpfGenericHostApplication. See New WPF application.

Splash Screen

Requires: Meteion.Toolkit.WPF.SplashScreen

Shows a native splash screen before WPF starts, and hands off to your launch window. See Splash Screen.

Unlike the default WPF splash screen, this one can show progress and status text.

WPF MVVM

Requires: Meteion.Toolkit.WPF.MVVM

WPF extensions for MVVM. Includes default implementations of INavigationService, IPageResolutionService, and IWindowResolutionService.

  • Navigation Management: Simplifies navigation for views and view models. INavigationService navigates by view model type (NavigateTo<TViewModel>()), keeps a back stack (GoBack(), CanGoBack, BackStackStatusChanged), can block navigation (IsNavigationLocked, for example while a form has unsaved changes) and can clear the stack (CleanNavigation()).

Nothing is registered for you: add AddScoped<INavigationService, NavigationService>() and the page and window resolution services (UseDefaultPageResolutionService, UseDefaultWindowResolutionService) to your services, as the sample app does. See New WPF application.

Converters

Requires: Meteion.Toolkit.WPF

Common value converters in the Meteion.Toolkit.WPF.Converters namespace. Where a converter exposes a static Instance, you can use it straight from XAML without declaring a resource:

xmlns:conv="clr-namespace:Meteion.Toolkit.WPF.Converters;assembly=Meteion.Toolkit.WPF"

<TextBlock Visibility="{Binding IsBusy, Converter={x:Static conv:BooleanToVisibilityConverter.Instance}}" />

Most converters return DependencyProperty.UnsetValue when the input isn't something they can convert. The exception is BackgroundToForegroundConverter, which returns white for anything that is not a solid colour brush.

Converter Converts Notes
BooleanToVisibilityConverter bool → Visibility true is Visible, false is Collapsed.
InverseBooleanToVisibilityConverter bool → Visibility false is Visible, true is Collapsed.
InverseBooleanConverter bool → bool Negates the value.
VisibleIfNullConverter object → Visibility Visible when the value is null, otherwise Collapsed.
VisibleIfNotNullConverter object → Visibility Visible when the value is not null, otherwise Collapsed.
VisibleIfNullOrEmptyConverter string/collection → Visibility Visible when null, an empty string, or an empty collection (handy for "no results" messages).
VisibleIfNotNullOrEmptyConverter string/collection → Visibility Visible for a non-empty string or collection; any other non-null object counts as Visible.
ToUpperConverter / ToLowerConverter string → string Changes the casing of the text.
DateOnlyToDateTimeConverter DateOnly ⇄ DateTime Works both ways, e.g. for binding a DateOnly to a DatePicker. Not available on the net48 target.
BackgroundToForegroundConverter SolidColorBrush → SolidColorBrush Picks black or white text for readability on the given background. Also usable as a MultiBinding converter.

Localization

See the Localization docs for usage and tooling guides.

The Localization library allows for language switching at runtime (unlike the default WPF one). It also helps with binding through {lx:LocalizedValue KeyBinding={Binding ...}} for most instances, and {lx:LocalizedBinding} for one-way localized bindings for things like DataGrid columns and other BindingBase properties. See Localization to get started.

Multiple resx files are supported, using generated keys that name their own resx. See Multiple resx files.

It also supports runtime culture switching, change the app's language independently of the OS locale, keeping CultureInfo.CurrentCulture, resx lookups, and FrameworkElement.Language all in sync. See Changing the current culture at runtime.

{lx:CultureAwareFormat} formats bound numbers/dates/currency using the app's current culture, live. See Culture-aware number/date/currency formatting.

Localization key checking (build-time, optional)
  • Localization Key Checking: Catches missing/undefined localization keys before you run the app. No runtime dependency and no other toolkit package required. See Localization key checking.
Localization key autocompletion (build-time, optional)
  • Localization Key Autocompletion: Generates a strongly-typed class from your .resx keys for autocompletion in code-behind and XAML. A build-time analyzer only; the generated keys are plain constants. See Key autocompletion.

Very very useful because you can {x:Static} your keys from XAML, helping reduce errors.

Recommendations

We recommend using this alongside CommunityToolkit.Mvvm for a complete MVVM experience.

FAQ

Q: Why use Meteion.Toolkit.WPF.MVVM and .Hosting instead of CommunityToolkit.IoC?

A: The CommunityToolkit.IoC is a simple IoC container that is not designed for complex scenarios. Meteion.Toolkit.WPF.MVVM and .Hosting provide a more robust solution for dependency injection and application hosting in WPF applications. It really helps makes your application feel like WPF was designed with Dependency Injection in mind. It also supplies some opinionated defaults, or can be adapted to your use case.

Q: Why use Meteion.Toolkit.Localization instead of {x:Static } or Properties.Resources.Blah?

A: The localization library includes a lot of helpful features, such as binding keys, changing the language at runtime (with CultureInfo.CurrentCulture and FrameworkElement.Language kept in sync automatically), and culture-aware number/date/currency formatting that updates live when the language changes.

License

MIT.

AI Use in this Project

Mostly just for docs, but I do use it to add comments in the code as well as for the source generators - there is no way I would have had the time to figure those out myself.

Product Compatible and additional computed target framework versions.
.NET net8.0-windows7.0 is compatible.  net9.0-windows was computed.  net10.0-windows was computed.  net10.0-windows7.0 is compatible. 
.NET Framework net48 is compatible.  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.8.0 113 10/22/2026
1.7.3 111 10/15/2026
1.7.2 96 10/15/2026
1.7.1 104 10/15/2026
1.7.0 100 10/14/2026
1.6.1 89 10/8/2026
1.6.0 101 10/8/2026
1.5.0 114 10/7/2026