WPF Toolkit - Preview

Rating:        Based on 9 ratings
Reviewed:  4 reviews
Downloads: 21946
Released: Aug 11, 2008
Updated: Aug 11, 2008 by VarshaMahadevan
Dev status: -not yet defined by owner-

Recommended Download

Application WPFToolkit_Binaries.zip
application, 86K, uploaded Aug 11, 2008 - 12149 downloads

Other Available Downloads

Source Code WPFToolkit_SourceAndBinaries.zip
source code, 271K, uploaded Aug 11, 2008 - 9797 downloads

Release Notes

The WPF Toolkit is a collection of WPF features and components that are being made available outside of the normal .NET Framework ship cycle. The WPF Toolkit not only allows users to get new functionality more quickly, but allows an efficient means for giving feedback to the product team. Many of the features will be released with full source code as well. Over time, some of these features may be moved into the .NET Framework, based on readiness and customer feedback.

This is a Community Tech Preview (CTP) Release of the DataGrid control. The download links on this page include a binaries only and a binaries & sources release package. You can also browse or download the source code under the Source Code tab.

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

Instructions for using the WPF Toolkit Preview binaries:
  1. Install .NET Framework 3.5 SP1
  2. Download and unzip the WPFToolkit_Binaries from the link above
  3. Reference the binaries in your project:
    1. Reference WPFToolkit.dll in your project
    2. Add a using statement ("using Microsoft.Windows.Controls;") to the top of .cs files
    3. Add a new xmlns (for example, xmlns:toolkit="http://schemas.microsoft.com/wpf/2008/toolkit") to the top of XAML files. Remember to use the namespace prefix (in the above example, <toolkit: ...>) in the body of your XAML.

Reviews for this release

     
This release is good, but there can be some improvement to the design of Visual State Management framework. Particualarly the following: 1) The VisualStateGroup property should be an ObservableCollection vs the manila IList type. 2) Why must the VSM insist on having the VisualStateGroup property be embeded in the first child of a Control type? This is something that not an intuative design
by rashadrivera on Aug 1, 2009 at 9:16 PM
     
Fine for a CTP. I am looking forward to V1.
by ChangedDaily on Oct 22, 2008 at 6:02 PM
     
This release is certainly better than implementing your own but it still has many issues and there is no documentation or release notes. If you plan on using this be prepared to surf through the Issues and Discussions sections.
by 12055 on Sep 18, 2008 at 10:32 PM
     
Nice that you finally thought about it, congratulations
by Calin on Aug 28, 2008 at 7:47 PM