Soluling home   Document home

No name in XAML element

When Soluling scans XAML items, it has to get the context of each element. XAML lets you write perfectly valid XAML without entering a proper name for components. This raises some challenges to Soluling because the components might not contain any unique context value. If this is the case, Soluling uses element names and its index to create a unique context. The context created is unique but not necessarily permanent. If you add new components to your XAML, it might be that the index values of existing items change, causing a change in context. This might cause problems in your project, such as losing existing translations or even mixing two existing translations. To prevent this, you should always give a name for your XAML components. XAML supports multiple attributes for naming. They are x:Name, Name, x:Uid, Uid, and x:Key.

x:Name and Name

x:Name and Name attributes do the same job. Both give an id to the component and enable the component object so you can programmatically access the component.

x:Uid and Uid

x:Uid and Uid give an id to the component but does not enable the component object.

x:Key

x:Key is used to identify a style.

AutomationProperties.AutomationId

AutomationPropertie.AutomationId is used to identify an automation id.

See also Duplicate names in XAML.