Kinnara/ModernWpf is a server-side project on GitHub with 5.0k stars, written primarily in C#. Modern styles and controls for your WPF applications
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Modern Fluent styles and WinUI-inspired controls for Windows Presentation Foundation.
Get started
·
Gallery
·
Documentation
·
Discussions
ModernWPF is an independent, community-maintained library that brings Fluent
styling and modern controls to
Windows Presentation Foundation applications.
It runs directly on WPF; it is not WinUI and does not replace the WPF runtime.
[!IMPORTANT]
ModernWPF 1.x is the active preview line. The 0.9.x line is frozen and
unsupported. No maintenance updates, security fixes, or new 0.9.x releases
are planned.
[!NOTE]
ModernWPF is the product and display name. The repository and CLR
namespaces continue to use ModernWpf, and the NuGet package remains
ModernWpfUI.
What ModernWPF provides
Fluent styling for stock WPF controls, including Light, Dark, High Contrast,
and compact-resource behavior.
WPF ports of modern controls such as NavigationView, NumberBox,
ContentDialog, InfoBar, CommandBarFlyout, and ItemsRepeater.
Application, window, and element-level theme APIs with a consistent surface
across every supported target.
Modern window chrome, title-bar integration, layout helpers, and resource
primitives for existing WPF applications.
Source-backed compatibility audits and automated API, resource, theme,
accessibility, package, and runtime tests.
Relationship to WPF and WinUI
ModernWPF follows both upstream UI projects, but each has a different role:
Area
Upstream authority
ModernWPF strategy
WPF runtime, XAML, layout, and input
dotnet/wpf
Build directly on WPF and preserve WPF behavior.
Stock control styling
Official WPF Fluent resources
Use the platform Fluent theme on .NET 10 and a compatible ModernWPF backport on older supported targets.
Additional modern controls
microsoft-ui-xaml
Port current WinUI control APIs and behavior where WPF has no equivalent, documenting necessary WPF adaptations.
ModernWPF is not affiliated with or endorsed by Microsoft.
Project status
Line
Status
Policy
1.x
Active preview
Current development line. 1.0.0-preview.1 records the first API/resource audit and migration baseline; the 1.0 roadmap carries source-audited feature previews through an API-frozen release candidate before stable 1.0.0 establishes the SemVer boundary.
0.9.x
Frozen and unsupported
Historical packages remain available, but no updates or security fixes are planned.
Source and binary compatibility with 0.9.x is not promised. Existing
applications should follow the
0.9.x migration guide, which covers target
framework changes, resource entries, renamed APIs, and the removal of the
MahApps adapter from 1.x.
Supported targets
Target framework
Stock control theme
Intended use
net462
ModernWPF Fluent backport
Existing .NET Framework WPF applications.
net8.0-windows7.0
ModernWPF Fluent backport
Modern .NET WPF applications targeting .NET 8.
net10.0-windows7.0
Official PresentationFramework.Fluent theme
Modern .NET WPF applications targeting .NET 10.
Retired net45, netcoreapp3.0, and net5.0-windows package assets are not
part of the 1.x line.
Getting started
Install an explicit 1.x version so NuGet does not select a frozen 0.9.x
package:
FluentControlsResources uses official WPF Fluent resources for stock controls
on net10.0-windows7.0 and the ModernWPF backport on the older supported
targets. Applications that need a staged migration may temporarily retain
ThemeResources plus XamlControlsResources; new applications should use the
recommended entry above.
Gallery
ModernWpf.Gallery is this repository's interactive
catalog and development sample. It demonstrates ModernWPF controls, WPF stock
controls, themes, window chrome, navigation, dialogs, flyouts, and input
behavior. It is a project sample, not Microsoft's official WPF or WinUI
Gallery.
On Windows, install the SDK selected by global.json, then run:
Use net8.0-windows7.0 to exercise that supported target. Building net462
also requires the .NET Framework 4.6.2 Developer Pack. In Visual Studio, open
ModernWpf.sln and select ModernWpf.Gallery as the startup project.
Documentation
Resource
Purpose
1.0 roadmap
Planned feature previews, the API-frozen release candidate, downstream evidence, and stable graduation rules.
1.0.0-preview.7 release notes
ItemsView selection, invocation, layout, transitions, WPF adaptations, and migration information.
1.0.0-rc.1 release notes
Public surface freeze, stabilization fixes, and RC acceptance requirements.
1.0.0-preview.6 release notes
ItemContainer, LinedFlowLayout, transition and scrolling prerequisites, WPF adaptations, and migration information.
1.0.0-preview.5 release notes
TabView milestone, WPF tear-out adaptation, validation, and preview limitations.
1.0.0-preview.4 release notes
TitleBar, Mica, Desktop Acrylic, fallback behavior, and migration information.
1.0.0-preview.3 release notes
TimePicker and TwoPaneView APIs, WPF adaptations, and migration information.
1.0.0-preview.2 release notes
Synchronization, packaging, migration, and known-preview information.
1.0.0-preview.1 release notes
Package changes, intentional 0.9 breaks, recommended resources, and preview limitations.
Migrating from 0.9.x
Step-by-step application migration guidance.
1.x public API contract
Preview governance and stable compatibility policy for CLR APIs and public resource keys.
Building requires Windows, the .NET SDK selected by global.json,
and the Visual Studio .NET desktop development workload or equivalent build
tools. The net462 target also requires the .NET Framework 4.6.2 Developer
Pack.
Restore and build serially from the repository root:
See release readiness for the complete test,
package verification, and executable consumer-smoke commands. Solution builds
and test builds should not run in parallel because WPF projects can contend for
shared intermediate files.
Contributing and feedback
Use Discussions for
questions, design ideas, and broader proposals.
Use the structured Preview bug form
for reproducible 1.0 preview problems, and Issues
for focused feature requests.
Read the related source-audit document under docs before changing a
WinUI-derived control or stock WPF template.
Add focused regression coverage and run the affected test project before
submitting a change.
License
ModernWPF is licensed under the MIT License. WPF and WinUI source
references retain their respective upstream notices and licenses.
The most recent commit recorded on Kinnara/ModernWpf was 2 days ago, based on the GitHub push timestamp. The repository has 488 forks — one of the better signals of community interest.
How many stars does Kinnara/ModernWpf have?
Kinnara/ModernWpf has 5.0k GitHub stars — refresh the page for the live number, or check github.com/Kinnara/ModernWpf. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the Backend space?
Kinnara/ModernWpf is tracked by TopGit under the Backend category, alongside 7 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is Kinnara/ModernWpf written in?
Kinnara/ModernWpf is written primarily in C#. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is Kinnara/ModernWpf associated with?
GitHub's repository topics for Kinnara/ModernWpf: "csharp", "desktop", "fluent-design", "windows", "winui", "wpf", "xaml". TopGit's editorial category is Backend.
Where do I read more about Kinnara/ModernWpf?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/Kinnara/ModernWpf is the definitive source.
Why is Kinnara/ModernWpf categorized under Backend?
TopGit places Kinnara/ModernWpf in the Backend category based on its GitHub topics and description (tagged: "csharp", "desktop", "fluent-design"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Is ModernWpf worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of ModernWpf.