Autogenerated by MFractor v3.2.0

Edit Color Declaration

Professional Only

Configuration Id: com.mfractor.code_actions.xaml.edit_inline_color

The Edit Color Declaration code actions allows visual editing of colors from your Xaml.

Simply right click on a Xaml node that is a System.Drawing.Color or Xamarin.Forms.Color and select Edit Color. Then you can use the color picker dialog to select a new color value:

Edit colour refactoring action

Extract Attribute Value Into Property Binding

Professional Only

Configuration Id: com.mfractor.code_actions.xaml.extract_into_property_binding

When a Xaml attribute is initialised by a literal value (rather than an expression), this refactoring action allows a developer to extract that literal value as a property into the binding context and replace the attribute initialiser with a binding expression.

For example, given the attribute initialiser Text=\"Hello Xamarin.Forms!\", this refactoring would generate a user named property (EG: Message) in the binding context, initiliase it with the string literal \"Message\" and replace the attribute value with the binding expresion {Binding Message}.";

Extract value into property binding


Migrate OnPlatform Usage

Professional Only

Configuration Id: com.mfractor.code_actions.xaml.migrate_on_platform_usage

In Xamarin.Forms 2.3.4, there were changes made to the OnPlatform class to enable greater platform-specifics flexibility in the future. These changes deprecated the OnPlatform.iOS, OnPlatform.Android and OnPlatform.WinPhone properties in favour of a generic On element to control the platform specifics.

The Migrate OnPlatform Usage code action is a refactoring that converts a pre-2.3.4 Xamarin.Forms OnPlatform usage to the new methodology using the nested On element.

For example, given the following OnPlatform:

<OnPlatform x:TypeArguments="Thickness" 
            Android="0, 0, 0, 0" 
            iOS="0, 20, 0, 0">
        0, 0, 0, 0

MFractor would migrate the code to use the On element:

<OnPlatform x:TypeArguments="Thickness">
    <On Platform="Android">0, 0, 0, 0</On>
    <On Platform="iOS">0, 20, 0, 0</On>
    <On Platform="WinPhone">0, 0, 0, 0</On>

Example of using the Migrate OnPlatform usage XAML refactoring

Migrate Value To Localised String

Professional Only

Preview Feature

Configuration Id: com.mfractor.code_actions.xaml.migrate_value_to_localised_string

Converts a


Rename Code Behind Field Declaration

Professional Only

Preview Feature

Configuration Id: com.mfractor.code_actions.xaml.rename_code_behind_field

Renames a code behind field declaration

Rename Xaml Namespace

Professional Only

Configuration Id: com.mfractor.code_actions.xaml.rename_xaml_namespace

The Rename Xaml Namespace code action will perform a symbolic rename-refactor on a particular Xaml within your document.

This is handy as you can then rename namespaces in a document without using a Find+Replace action; the rename xaml namespace action works against symbols so it will always rename only the namespace symbols.

To action this refactoring:

  • Within a Xaml document right click or Alt+Return on an xmlns attribute (EG: xmlns:local="clr-namespace:myApp")
  • Select Refactor.
  • Then Rename Namespace.
  • Enter a new namespace name when prompted and then click enter.

Your new namespace will be applied across the document:

Renaming a Xamarin.Forms Xaml namespace