Is there any difference in x:name and name for controls in xaml file?

by

In Brief

Yes there is a difference. The bottom line is that x:Name can be used on object elements that do not have Name properties of their own.

A longer explanation

You can only use Name on an element that represents an object that actually does have a Name property. For example anything that derives from FrameworkElement.

The x:Name attribute may be placed on any element that represents an object regardless of whether that object actually has a Name property. If the object does have a Name property then the value of x:Name will be assigned to it hence you can’t have both x:Name and Name on the same element.

When an object has a Name property or an x:Name property the value of that property is associated with the objects entry in the object tree. It is via the object tree that the FindName method of a FrameworkElement can find an object. FindName can find objects by name even if that object does not carry a Name property of its own since it uses the name recorded in the object tree.

The autogenerated code for a UserControl will contain field definitions for any element that that has a Name or x:Name property. The InitialiseComponent method that is generated will use the FindName method to assign values to these fields.

Example

The above Xaml creates two fields LayoutRoot of type Grid and MyBrush of type SolidColorBrush. If you were to change x:Name="LayoutRoot" to Name="LayoutRoot" that would change nothing. Grid has a Name property. However try changing x:Name="MyBrush" to Name="MyBrush". That doesn’t work because SolidColorBrush doesn’t have a name property. With the above Xaml you can then do code like this:-

    public MainPage()
    {
        InitializeComponent();
        MyBrush.Color = Colors.LightGray;
    }

Open the definition of InitializeComponent and take a look at the auto generated code.

More Related Contents:

  1. Access ResourceDictionary items programmatically
  2. Difference between SelectedItem, SelectedValue and SelectedValuePath
  3. This type of CollectionView does not support changes to its SourceCollection from a thread different from the Dispatcher thread [duplicate]
  4. Getting Started with Windows Phone 7 [closed]
  5. Binding to ActualWidth does not work
  6. How to access a specific item in a Listbox with DataTemplate?
  7. Display GIF in a WP7 application with Silverlight
  8. How do you force Firefox to not cache or re-download a Silverlight XAP file?
  9. Creating a Silverlight DataTemplate in code
  10. Dynamically setting the Header text of a Silverlight DataGrid Column
  11. Windows Phone 7 close application
  12. Binding [VisualStateManager] view state to a MVVM viewmodel?
  13. MVVM light – how to access property in other view model
  14. Bind Collection to StackPanel
  15. Access codebehind variable in XAML
  16. The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range?
  17. How Do I Give a Textbox Focus in Silverlight?
  18. Invalid cross-thread access issue
  19. Databinding TextBlock Runs in Silverlight / WP7
  20. Accessing static fields in XAML
  21. What is the difference for TargetType=”{x:Type Button}” and TargetType=”Button”?
  22. Iterating through an enumeration in Silverlight?
  23. Adding a Merged Dictionary to a Merged Dictionary
  24. How to zoom in and zoom out Images in WP7?
  25. Silverlight: image to byte[]
  26. How to programmatically set selected Panorama item in WP7
  27. How to hide close button in WPF window?
  28. How to create custom window chrome in wpf?
  29. Cannot find source for binding with reference ‘RelativeSource FindAncestor’ [duplicate]
  30. WCF HttpTransport: streamed vs buffered TransferMode

Leave a Comment