Працюючи з WPF, мене сильно цікавило застуосування унаслідуваних (Inherits) пропертей (особливо в світлі того наскільки "дорогі" біндінги (Binding)),

I am glad to announce that the new CTP of the Blend 2 is out

First of all, what is this misterious thing, MarkupExtension? As it follows from it's name, this is some kind of the extension for the XAML markup syntax, and in our case that is an the extension that allows user to shorten or simplify some operations in XAML, or at least provide some non-string data in case TypeConverter can not be used. One of the most common examples of the MarkupExtension is a shortened declaration of a data binding, like {Binding Path}. {StaticResource key} is also widely used, and that is also a MarkupExtension. Both of them can be declared in element syntax, but that is not widely used because the amount of XAML needed in such case is a bit larger, so I will use attribute syntax in my samples.

I have just found out one cool feature in WPF: there is one cool markup extension called ThemeDictionaryExtension, that can provide ResourceDictionary, associated with a current theme.

Думаю, уже об этом многие читали, но я осмелю повториться: очередная версия Бленда увидила свет: Expression Blend 2 September Preview уже доступен к скачиванию.

... >>>

Off and on I try and use the UIAutomation libraries from .NET 3.0 for a variety of things. Most often it is testing but not always. Since I do more unit testing than anything else I find LogicalTreeHelper, VisualTreeHelper and the AutomationPeer functionality more useful than AutomationElement.
On a recent project we were doing some work on a screen that wasn't particularly easy to get to. It took about 9 clicks. Not that bad but I'm lazy. We were doing a lot of fancy WPF stuff and we really wanted to see things live in the full application context instead of in Blend or just raw xaml. So we would run the app a lot. I got tired of doing the same clicks and occasionally making mistakes just to get the screen to show. So I chose to write a small app that would use UIAutomation to get me to the screen. Seemed simple enough. I've done plenty of work with UIAutomation and I thought it would be easy. Was I in for a suprise.
... >>>

Introduction

In this part we will closely examine such fundamentals of UI Automation as:

• UI Automation control patterns
• UI Automation properties
• UI Automation events

And in the end, we will try to implement a simple UI Automation support for custom control.