Controls

Installation and Usage Instructions

Please note: The Extended WPF Toolkit is dependent on .NET Framework 4.0. You must install .NET Framework 4.0 in order to use any features in the Toolkit.

Instructions for using the Extended WPF Toolkit binaries:

  1. Install .NET Framework 4.0.
  2. Download the ExtendedWPFToolkit_Binaries
  3. Unblock the ZIP file.
    1. Right-click ExtendedWPFToolkit_Binaries.zip -> Properties -> Unblock
  4. Unzip the ExtendedWPFToolkit_Binaries.zip
  5. Reference the binaries in your project:
    1. Reference WPFToolkit.Extended.dll in your project (Xceed.Wpf.DataGrid.dll for the datagrid control)
    2. Add a using statement ("using Xceed.Wpf.Toolkit;" for most of the controls, "using Xceed.Wpf.DataGrid;" for the datagrid control) to the top of .cs files
    3. Add a new xmlns (xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" for most of the controls, xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid" for the datagrid control) to the top of XAML files
    4. Remember to use the namespace prefix (in the above example, <xctk: ...> or <xcdg: ...>) in the body of your XAML

Installation using NuGet

  1. Install NuGet (can be downloaded for this link).
  2. Open your Visual Studio.
  3. Open your solution/project.
  4. Open Tools menu, select Library Package Manager and select Package Manager Console
  5. Run the following command Install-Package Extended.Wpf.Toolkit
    1. Add a using statement ("using Xceed.Wpf.Toolkit;" for most of the controls, "using Xceed.Wpf.DataGrid;" for the datagrid control) to the top of .cs files
    2. Add a new xmlns (xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" for most of the controls, xmlns:xcdg="http://schemas.xceed.com/wpf/xaml/datagrid" for the datagrid control) to the top of XAML files
    3. Remember to use the namespace prefix (in the above example, <xctk: ...> or <xcdg: ...>) in the body of your XAML


Last edited Nov 26, 2013 at 5:45 PM by emartin, version 61

Comments

BoucherS Jan 14 at 5:48 PM 
Hi, Please use a discussion Tab !
For the problem : Make sure to reference the Xceed.Wpf.Toolkit and xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" at top of your xaml file.

wcom939 Jan 9 at 7:33 PM 
When installing as specified in the instructions for NuGet in VS 2012, when attempting to add the button spinner, with the code I get the following errors:
"Cannot Resolve Symbol Control" For Microsoft.Windows.Controls.SpinEventArgs
and Microsoft.Windows.Controls.SpinDirection.Increase

I also receive cannot resolve symbol Direction for e.Direction

used code as stated in the buttonspinner example.

Thanks

Dills1002 Dec 23, 2013 at 12:40 AM 
Hi,

I receive the following error when I try to run a project containing a reference to this library:

"Could not load file or assembly 'Xceed.Wpf.Toolkit, PublicKeyToken=3e4669d2f30244f4' or one of its dependencies. The system cannot find the file specified."

To confirm, this only happens at runtime. I have been able to add controls from the library through the XAML Designer without any problems.

The DLLs are all in the location in which the project is executing from. I'm using VS 2012 Pro & Win 7 and my project is targeting .NET 4. I have unblocked each of the DLLs.

Any ideas? I'm tearing my hair out over this!

Thanks.

Base12 Jun 2, 2013 at 10:24 PM 
Installtion tip: To make it easier to see all the controls in VS (I'm using 2010). You can add them to the Toolbox for drag and drop. On the Toolbox,, Right-click and select "Add Tab" and call it. WPF Tollkit Extended. Right-click on this new Tab that appears in your Toolbox and select "Choose Items" Select the "WPF Components" tab. In the Access Text section, click on "Browse" button. Look for and select the WPFToolkit.Extended.dll file. The controls will be added to the list and have a check mark on them, simply click ok. Now, the controls are in your New Tab and you can drag and drop them.

Wuffles May 21, 2013 at 1:20 PM 
Thankyou sstorie, I had the exact same problem and you just no doubt saved me a lot of googling!

sstorie Feb 23, 2013 at 4:14 PM 
In case this might save someone else some time I ran into an issue with this latest release that I needed to find the following link to figure out:

http://msdn.microsoft.com/en-us/library/ee890038(VS.100).aspx

In short, I could add the new assemblies to VS 2010, and my solution would build fine, but the XAML editor acted as though the assemblies were missing. In my XAML code when I used "<xctk:..." nothing would resolve even though I had the right xmlns tag at the root.

Arvind27 Jan 2, 2013 at 8:37 AM 
Hi there,
When I am trying to add using statement I am getting the following error "type or namespace name "XCEED" could not be found". I am using VS2008.
Please help me on this.

emartin Nov 15, 2012 at 12:59 AM 
http://wpftoolkit.codeplex.com/releases/view/94866
Under "Interface changes" :
- MaskedTextBox.ValueType replaced by MaskedTextBox.ValueDataType
Please use discussion tab for help requests

inveganatheist Nov 14, 2012 at 5:42 PM 
When using ValueType="{x:Type sys:Int32}" with a xctk:MaskedTextBox I get the error
"The property 'ValueType' does not exist in XML namespace 'http://schemas.xceed.com/wpf/xaml/toolkit". The previous version of the toolkit didn't have this error