Open-source project
xceedsoftware/wpftoolkit avatar
xceedsoftware/wpftoolkit

Extended WPF Toolkit: free controls, wiki-hosted docs, and two edition tracks

All the controls missing in WPF. Over 1 million downloads.

4,175 stars906 forksC#NOASSERTION

At a glance

What is it?
Xceed's Extended WPF Toolkit ships about fifty WPF controls and utilities, free for non-commercial use since version 4.0.0 under a licence that lives in one file at the repository root. Its README is a link table into a wiki the repository does not contain, and its news list gives the same version number to the free line and to the paid Plus Edition.
Who is it for?
Use the Extended WPF Toolkit when you are building a WPF desktop application, you do not need the DataGrid, the charts or the Material Design set, and the work is non-commercial.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 157 days ago.
What is it written in?
Mainly C#, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • xceedsoftware/wpftoolkit4,175 ★ · +5
Star history
Repository2026-09-232026-11-15
xceedsoftware/wpftoolkit4.2k4.2k

5 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The free edition stops at non-commercial work

The licence field shown for this project on its hosting page reads NOASSERTION, so no terms can be read off the project summary. The actual terms sit in one file at the repository root, license.md, and the README points at it with a single sentence: starting at version 4.0.0 the toolkit is provided free under the Xceed Community License agreement for non-commercial use.

That version boundary is the part worth holding on to. Anything from before 4.0.0 was not distributed under that agreement, and license.md is the only copy of the terms in this repository. Nothing else in the tree repeats them.

For a commercial desktop product, the free download does not answer the licensing question. The same README sentence routes that case to the Plus Edition, which is sold separately, is not in this repository, and cannot be read from here. So the decision splits cleanly: read license.md first, and if your product ships for money, treat the free download as not applicable rather than as free.

Every control name links to a page the repository does not hold

The controls are presented as a single HTML table of about fifty cells, and every cell is an anchor whose target begins ../../wiki/ followed by a page name. That path climbs two directories above this README, so the pages it names are not files in the repository. The five things at the top level are .gitignore, ExtendedWPFToolkitSolution/, README.md, _config.yml and license.md, and none of them is a documentation directory.

The consequence for a reader is concrete. Names such as PropertyGrid, MaskedTextBox, ByteUpDown, MultiLineTextEditor and WatermarkPasswordBox are visible, so you can see that the control exists and roughly how large the set is, but no property, no event and no usage snippet is available anywhere in this repository. Adoption decisions therefore depend on pages the repository cannot show you.

The same table also reveals the shape of the set without describing it: fifteen numeric and time spinner controls including ByteUpDown, ShortUpDown and TimeSpanUpDown, four watermark inputs, a ChildWindow, a BusyIndicator, a Magnifier, a PieChart, a TimelinePanel and a Wizard. The breadth is legible; the mechanics are not.

The free and paid tracks share one version number

The news list gives version 5.1.0 to the free line on June 11, 2026 with 12 bug fixes and improvements. It also gives version 5.1.0 to the Plus Edition on March 16, 2026, described as a ServiceRelease with 5 bug fixes and improvements, and gives version 5.1.0 to the Plus Edition again on September 9, 2025 with 22 bug fixes and improvements.

Three entries, one version number, two products. On the same day, September 9, 2025, the free line released 5.0.0 while the Plus Edition released what it calls 5.1.0.

This matters for anything that treats a version as a unique artefact. The repository itself carries only three release tags: 5.1.0 from June 11, 2026, 5.0.0 from September 9, 2025 and 4.7.0 from March 10, 2025. The shared version number alone does not identify the edition; check package identity, feed and licence when pinning a build, and the README gives you no way to tell a community build from a Plus build by version alone. The news dates do the work that the numbers cannot.

Plus Edition fix lists point at a page named for version 3.5.0

Free-line entries link to pages named after their own version: Improvements-in-v5.1.0, Improvements-in-v5.0.0, Improvements-in-v4.7.0 and Improvements-in-v4.6.1. Each Plus Edition entry instead links to Improvements-in-v3.5.0 with an anchor, for example #Plus510, #Plus500, #Plus470 and #Plus461.

So the paid track accumulates its change history on a single page named after a release three major generations back, while the free track gets a fresh page per version. That is a workable convention, provided the anchors stay in sync. No file matching Improvements-in-v3.5.0 exists in this repository either, so the anchors cannot be verified from the source tree.

If you need to know what changed in a particular Plus Edition release, you have to resolve an anchor on a page outside this repository and trust that the anchor text still matches its section. Reading the free line's fix list needs no such trust.

One download figure, three hosting sites, no split

The opening paragraph claims more than 1 million downloads and attributes them to three places: here on the repository, on Codeplex, and on NuGet. The NuGet link resolves to the package page for Extended.Wpf.Toolkit.

A single count across three sources cannot be attributed to any of them, and the claim carries no date, so there is no way to tell how much of it arrived through the current package feed and how much predates it. The number functions as a rough indicator of how long the toolkit has been available rather than as a measurement of current use.

Two details about how the link is written are worth knowing. It is an http URL with a trailing slash rather than an https one, and it targets the package page rather than a version, so a reader following it lands on whatever the current release is rather than on a fixed build. Neither is wrong, but neither pins a version.

Windows 8 in the free table, Windows 10 in the paid table

The last row of the free controls table offers a Windows 8 Theme. The last row of the Plus Edition table offers a Windows 10 theme, and both cells point at the same wiki page, Themes-Usage-Instructions.

So the two editions ship different default themes and share one set of instructions. A project that starts from the free table and follows that page gets documentation written for both. Windows 8 as the newest theme offered for free is the number that tells you the age of the free edition's visual defaults, and it is one of the clearest signals in the README about how far the two tracks have diverged.

The Plus table is also the only place certain control shapes appear: 21 Material Design controls, a DataGrid, charts, a FilePicker, a RadialGauge, a Rating, a ToggleSwitch and 12 new SwitchPanels, where the free table advertises 2 SwitchPanels under a single page.

One solution folder, a Pages config, and no build steps

The top level is .gitignore, ExtendedWPFToolkitSolution/, README.md, _config.yml and license.md. No solution file sits at the root, so the buildable tree is one directory down, and the C# code is in there.

_config.yml belongs to a GitHub Pages site rather than to a C# build, and the README's raw HTML table confirms that the page is written to be rendered on a Pages site. The default branch is master, not main, which is worth knowing before you write automation against it.

No build instruction, package manager invocation, minimum Windows version or target framework version appears anywhere in the README. The only acquisition route the project names is the NuGet package page for Extended.Wpf.Toolkit. So version compatibility has to come from the package feed itself or from the wiki, and this repository will not tell you which .NET version a given release targets.

Editorial conclusion

Use the Extended WPF Toolkit when you are building a WPF desktop application, you do not need the DataGrid, the charts or the Material Design set, and the work is non-commercial. Check three things before committing: the Community License terms in license.md against your own licensing model, the wiki page for the specific control you plan to adopt, since this repository carries no control documentation of its own, and the framework target of the release you install, which is not stated anywhere in the repository. Look at the Plus Edition only if a business product needs it, since commercial use is exactly the case the free download does not cover.

Frequently asked questions

What is the WPF Toolkit maintained by xceedsoftware?

It is a collection of WPF controls, components and utilities for Windows desktop applications, about fifty named entries in the free edition's table, plus a separately sold Plus Edition with the DataGrid, charts and Material Design controls.

How do you use the Extended WPF Toolkit?

This repository documents no usage steps. Control names sit in an HTML table whose links climb out of the repository into a wiki, and the only acquisition route named is the NuGet package page for Extended.Wpf.Toolkit.

Which licence covers the free Extended WPF Toolkit?

The Xceed Community License agreement, for non-commercial use, starting at version 4.0.0. The terms are in license.md at the repository root, while the licence field on the hosting page reads NOASSERTION.

Does this repository contain the Extended WPF Toolkit Plus controls?

No. The Plus Edition is a separate paid product that the README only names in a table of extra controls, so its code and its documentation are not part of this repository.

What target framework does the Extended WPF Toolkit build against?

The repository does not say. No target framework or minimum Windows version appears in the README or among the five top-level entries, and the buildable code sits inside ExtendedWPFToolkitSolution rather than at the root.

Which Extended WPF Toolkit version was released most recently?

Version 5.1.0, released June 11, 2026 with 12 bug fixes and improvements, and the same day is the most recent push to this repository. The two releases before it are 5.0.0 on September 9, 2025 and 4.7.0 on March 10, 2025.

Official sources

  1. Issues
  2. README
  3. Releases
  4. xceedsoftware/wpftoolkit on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xceedsoftware-wpftoolkit.svg)](https://hysenlabs.com/projects/xceedsoftware-wpftoolkit)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xceedsoftware-wpftoolkit.svg)](https://hysenlabs.com/projects/xceedsoftware-wpftoolkit)

Was this useful?