Wpftoolkit Versions Save

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

3.8.0

4 years ago

What's new in v3.8.0?

Released January 30, 2020

v3.8.0 provides 35 bug fixes and improvements. A lot of attention was put improving AvalonDock, including 15+ improvements. Check out the Plus Edition for more controls, features, and to get your hands on upcoming releases earlier.

Want an easier way to install Extended WPF Toolkit?

Extended WPF Toolkit v3.8.0 is available on NuGet as of January 30, 2020.

.NET Framework notes:

Requires .NET Framework 4 an up.

Instructions for using the Extended WPF Toolkit binaries:

  • Install .NET Framework 4 and up
  • Download the ExtendedWPFToolkit_Binaries
  • Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  • Unzip the ExtendedWPFToolkit_Binaries.zip
  • Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  • Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  • In your XAML, use the namespace prefix (in the above example, <xctk: ...>)

3.7.0

4 years ago

What's new in v3.7.0?

Released November 26, 2019

v3.7.0 provides 18 bug fixes and improvements. Keyboard movements and selections improved for CheckComboBox, selections + incrementations + keyboard movements improved for TimeSpanUpDown. Starting at v3.7.0, the Extended WPF Toolkit is provided under the Xceed Community License agreement(for non-commercial use). Check out the Plus Edition for more controls, features, and to get your hands on upcoming releases earlier.

Want an easier way to install Extended WPF Toolkit?

Extended WPF Toolkit v3.7.0 is available on NuGet as of November 26, 2019.

.NET Framework notes:

Requires .NET Framework 4 an up.

Instructions for using the Extended WPF Toolkit binaries:

  • Install .NET Framework 4 and up
  • Download the ExtendedWPFToolkit_Binaries
  • Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  • Unzip the ExtendedWPFToolkit_Binaries.zip
  • Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  • Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  • In your XAML, use the namespace prefix (in the above example, <xctk: ...>)

3.6.0

4 years ago

What's new in v3.6.0?

Released September 27, 2019

v3.6.0 provides 36 bug fixes and improvements. 14 of them are for AvalonDock, the docking windows control. Check out the Plus Edition for more controls, features, and to get your hands on upcoming releases earlier.

Want an easier way to install Extended WPF Toolkit?

Extended WPF Toolkit v3.6.0 is available on NuGet as of September 27, 2019.

.NET Framework notes:

Requires .NET Framework 4 an up.

Instructions for using the Extended WPF Toolkit binaries:

  • Install .NET Framework 4 and up
  • Download the ExtendedWPFToolkit_Binaries
  • Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  • Unzip the ExtendedWPFToolkit_Binaries.zip
  • Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  • Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  • In your XAML, use the namespace prefix (in the above example, <xctk: ...>)

3.5.1

5 years ago

What's new in v3.5.0?

Released February 7, 2019

v3.5.0 provides 26 bug fixes and improvements. 14 of them are for AvalonDock, the docking windows control. Also, the DataGrid control is now part of the Toolkit Plus for WPF. Check out the Plus Edition for more controls, features, and to get your hands on upcoming releases earlier.

Want an easier way to install Extended WPF Toolkit?

Extended WPF Toolkit v3.5.0 is available on NuGet as of February 7, 2019.

.NET Framework notes:

Requires .NET Framework 4 an up.

Instructions for using the Extended WPF Toolkit binaries:

  • Install .NET Framework 4 and up
  • Download the ExtendedWPFToolkit_Binaries
  • Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  • Unzip the ExtendedWPFToolkit_Binaries.zip
  • Add a using statement ("using Xceed.Wpf.Toolkit;") to the top of .cs files
  • Add a new xmlns (for example, xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit") to the top of XAML files
  • In your XAML, use the namespace prefix (in the above example, <xctk: ...>)