Soluling home   Document home

Scan Rule of XAML (WPF, UWP, Xamarin)

Scan Rule of XAML (WPF, UWP, Xamarin)

Use this dialog to edit a scan rule of XAML based resources.

Component type

Enter the type name of the component where the property belongs. Enter this value only if the property is component-specific. If you want to scan all the same name properties no matter the component's type, leave this value empty. The value can contain wild cards (* and ?). If the property rule is a rule of a component, this edit is hidden.

Note! When specifying a scan property, you can either include the name that is used in XAML (e.g., "Label") or the full namespace of the component type (e.g., "System.Windows.Controls.Label"). If the component is a custom component, you can also use the component type you use in XAML (e.g., "custom:MyCustomControl").

Property name

Enter the name of the property. You must enter a value. The value can contain wild cards (* and ?). If the property is an element value, type Content.

Operation

Specifies if the property is localized or not. Possible values are:

Exclude Properties matching this rule are not localized.
Localize Properties matching this rule are localized.
Hide Properties matching this rule are scanned but hidden.

Format

Select the type of property. Possible values are

Value Description
Default Soluling detects the property value and uses an appropriate parser to scan it.
String Property is scanned as plain text.
Integer Property is scanned as an integer value.
Float Property is scanned as a floating-point value.
Boolean Property is scanned as a boolean value.
Color Property is scanned as the color value.
Font name Property is scanned as a font name value.
Font size Property is scanned as a font-size value.
Reading order Property is scanned as a reading order value.
Input method editor Property is scanned as an input method editor value.

If you don't know the format, leave it to default. If the property you want to scan is so complex that default does not work and you can not use either expression or XML format, contact us to check if we can implement a dedicated parser for that property.