A while back I reported both through my weblog and Microsoft Connect what I thought was a serious flaw in the WPF validation infrastructure for ValidationRule and Binding. The issue, in short was: The validation check is invoked during any attempt to update the underlying data ... before a value converter...

WPF NavigationWindow is a very handy class that allows you to easily build Vista-like wizards, or any kind of window that resembles the browser-style navigation:    The NavigationWindow will automatically handle the Backspace, Back/Next keys and perform the appropriate navigation on...

Just issue the following PowerShell one-liner, and you'll compile and run each sample in the SDK (enter all in one line; broken here for readability): PS C:\WinFx Samples\WPFSamples\AppModel\> gci -i *.csproj -r | foreach { pushd ([System.IO.Path]::GetDirectoryName($_.FullName)); msbuild $_.fullname;...

From the new Clarius Labs release : XamlBinding Custom Tool This custom tool will generate a partial class file implementing INotifyPropertyChange as well as a strongly-typed event for each property declared in the file it's applied to. This is very useful when creating models or entities that are used...

WPF provides validation infrastructure for databinding scenarios through ValidationRule objects. Only one built-in rule is provided, and you're expected to write most of these yourself. The way they work is by assigning one or more explicit rules to a binding: <TextBox ...> <TextBox.Text>...

Adam Nathan 's excelent book on WPF states: The validation check is invoked during any attempt to update the underlying data ... before a value converter is called (if present)... This is further reinforced on MSDN where the validation process is explained : I can't understand how this design decision...

In my previous post about XAML and its future as a domain model/DSL serialization format , I've argued that System.Configuration as well as Enterprise Library Configuration (part of the core of EntLib) will soon become irrelevant. The caveat is that now you need to design your classes a bit differently...

It may seem unrelated, but if you haven't read Fowler's article on DSLs ( from Google cache if it's down like now ), please do so now. It will help you understand why XAML goes far beyond WPF and presentation. Configuration is typically nothing more than a DSL (external DSL in Fowler's terms) that serves...

Databinding in WPF is implemented in the Binding class, which in principle looks like just a MarkupExtension . A MarkupExtension is a core piece of XAML markup "magic". It's rather simple, though: public abstract class MarkupExtension { // Methods protected MarkupExtension(); public abstract object ProvideValue...

In order to develop WPF apps in VS2005, you must install the corresponding CTP tools for it. These will basically bring in some new project templates, project types, MSBuild taks and designers. The designers are quite slow, and don't always work as expected. Being a CTP, and with VS2008 ("Orcas") already...