elementname

What of the following TextBlocks' Bindings costs more performance: <Window x:Name="Me" x:Class="MainWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:src="clr-namespace:WpfApplication1" Title="MainWindow"> <StackPanel> <TextBlock Text="{Binding Title, ElementName=Me}"/> <TextBlock Text="{Binding Title, RelativeSource={RelativeSource AncestorType={x:Type src:MainWindow}}}"/> </StackPanel> </Window> I am sure my question might take different when the TextBlocks are in a high nesting level having many siblings

Having {Binding ElementName=foo} , will it lookup visual or logical tree? Of logical and visual trees in WPF | Data See, Data Do When does the logical tree matter? When looking up a name, such as in {Binding ElementName=Foo}, the search walks up the ancestry looking for a name scope, again just as it does for inheritable properties. ElementName binding in Silverlight via Attached Behaviours In order to enable this, WPF provides ElementName and RelativeSource bindings, giving you a powerful mechanism for locating other elements within your visual tree to bind to EDIT: It looks like the Logical

If I selected an element using XPATH how can I get its name? I mean something like text() function in //element/[@id=elid]/text() . Daniel Haley Use name() . (Find docs for newer versions of the XPath language here .) Here are modified versions of your example: Works in XPath 2.0 only: //element/*[@id='elid']/name() Works in XPath 1.0 and 2.0: name(//element/*[@id='elid']) You could also use local-name() which returns the local part of the expanded name (without any namespace prefix). The tag names tree can also be obtained with echo "du //Element/*" | xmllint --shell response-02.xml Ele1 id