Xamarin.Forms 4.7: Grid Column & Row Definitions, Multi-Bindings, Shapes & Paths, and More!

Jake Kirsch

Today, the Xamarin.Forms team is releasing Xamarin.Forms 4.7 with a collection of feature additions and improvements. These new features will let you unleash your full creative abilities when developing Xamarin.Forms applications.

Simplified Grid Row & Column Definitions

Before Xamarin.Forms 4.7, you would have to specify each column and row definition separately. This process was tedious and repetitive, thus leading to an overall slower design time. Thanks to Morten Nielsen’s enhancement request, column and row definitions have been simplified. Take this example below:

        <ColumnDefinition Width="1*" />
        <ColumnDefinition Width="2*" />
        <ColumnDefinition Width="Auto" />
        <ColumnDefinition Width="*" />
        <ColumnDefinition Width="300" />
        <RowDefinition Height="1*" />
        <RowDefinition Height="Auto" />
        <RowDefinition Height="25" />
        <RowDefinition Height= "14" />
        <RowDefinition Height="20" />

While this code is practical, it is overly complex. To help simplify the grid definition process, the Xamarin.Forms team has created a simplified syntax.

<Grid ColumnDefinitions="1*, 2*, Auto, *, 300"
    RowDefinitions="1*, Auto, 25, 14, 20">

Shorter, easier. Thanks, Morten!


The next great feature added to Xamarin.Forms in 4.7 thanks to the work of Peter Moore is multi-binding. Multi-binding allows you to connect a target property to a list of source properties and then apply logic to produce a value with the inputs specified.

A simple and powerful way to use multi-binding is the ability to format any multi-binding result that’s displayed as a string with the StringFormat property. This property can be set to a standard .NET formatting string, with placeholders, that specifies how to format the multi-binding result. For example, let’s say you wanted to create a label of a user’s full name. You can use multi-bindings combined with StringFormat to create a single label that contains the user’s full name, regardless of where the user inputs their forename, middle name, or surname. An example of this can be seen below:

        <MultiBinding StringFormat="{}{0} {1} {2}">
            <Binding Path="Employee1.Forename" />
            <Binding Path="Employee1.MiddleName" />
            <Binding Path="Employee1.Surname" />

Multi-binding is even more powerful when you add MultiValueConverters.

Shapes & Paths

Today in Xamarin.Forms we are releasing experimental support for shapes and paths. Currently, we have Views such as BoxView or Frames that allow you to create rectangles or ellipses. However, we recognize that you want the ability to create any shape that best fits your application design. Shapes & paths in Xamarin.Forms allow you to create custom, unique designs to better fit your user interfaces.

David Ortinau made an amazing login screen example to show what shapes and paths can add to your apps.

Image LoginShapes

There are many new features leveraged when creating this application. First, a custom image shape was created using the clip property.


In this example, an ellipse shape is supplied to the image clip property. However, you can use any shape as the clipping shape.

Another new feature shown in this example is drawing a path to create a custom login shape, and then the login button itself.

    Data="M251,0 C266.463973,-2.84068575e-15 279,12.536027 279,28 L279,276 C279,291.463973 266.463973,304 251,304 L214.607,304 L214.629319,304.009394 L202.570739,304.356889 C196.091582,304.5436 190.154631,308.020457 186.821897,313.579883 L186.821897,313.579883 L183.402481,319.283905 C177.100406,337.175023 160.04792,350 140,350 C119.890172,350 102.794306,337.095694 96.5412691,319.115947 L96.5273695,319.126964 L92.8752676,313.28194 C89.5084023,307.893423 83.6708508,304.544546 77.3197008,304.358047 L65.133,304 L28,304 C12.536027,304 1.8937905e-15,291.463973 0,276 L0,28 C-1.8937905e-15,12.536027 12.536027,2.84068575e-15 28,0 L251,0 Z"

In this case, a path view was defined within the XAML page, and then the data property was populated with path data that defines the custom shape.

It’s important to note that this feature is shipping under the experimental flag, and thus Shapes_Experimental must be added to your App.xaml.cs constructor. For much more information on using shapes and paths, check out the documentation.

Light & Dark mode

With Xamarin.Forms 4.7 the Xamarin team is releasing updates to style light and dark mode. Users now have even more control to manage the theme of their applications through the use of UserAppTheme.

Image apptheme

Before you get started, set the experimental flag for AppTheme_Experimental. You can now set the style of your application with AppThemeBinding, and see your UI update at runtime as the OS changes theme. To do so, set the value of the property you are binding to using AppThemeBinding, as seen below:

<Style TargetType="ContentPage" ApplyToDerivedTypes="True">
    <Setter Property="BackgroundColor" 
        Value="{AppThemeBinding Dark={StaticResource BackgroundColor_Dark},
            Light={StaticResource BackgroundColor_Light}}"/>

Note, if you were using AppThemeColor in a previous version, you’ll need to update to this.

You can also set the app theme regardless of what your operating system’s theme is currently set to. For example, if your phone is in Light mode, but you want the specific app you are using to be in dark mode, then you can set:

Application.Current.UserAppTheme = OSAppTheme.Dark;

To keep the app theme on light mode regardless of your operating system’s application theme, set your application to:


If you want your application to default to your operating system’s application theme, set your application to:


Read more about Light and Dark mode on the Xamarin.Forms docs.

Every release we have dozens of contributors, and several of whom we mention in our blogs. Today we are starting a featured spotlight to learn a little bit more about a contributor, so today let’s meet Fredy.

What’s your name?
Fredy Adriano Jimenez Martinez

Where are you based?
I’m Cuban, but living in Mexico.

How long have you been using Xamarin.Forms?
10 months

Where can people find you online?

Get Started Today

Update your projects from your favorite NuGet package manager today! Take advantage of this latest release. Share your projects and progress with us online.

We’d love your feedback on Xamarin Forms. Please open issues on GitHub for any additional enhancements or issues to discuss. For more information on this release check the resources below.


Discussion is closed. Login to edit/delete existing comments.

  • Indudhar Gowda 0

    Nice..Can we drag this features to uwp as well..
    I am talking about only uwp not xamarin.

  • Alexandre Sanlim - Programador Libertário 0

    “Simplified Grid Row & Column Definitions” It’s very nice!

  • Kalixt Huska 0

    Very nice update.

  • Jinming Mu 0

    giving a alias to ColumnDefinition/RowDefinition is better than this so controls can quickly locate themselves Not only via index.
    ” Simplified Grid Row & Column Definitions” is useless and NOT elegant.

  • saint4eva 0

    The Grid improvement is excellent

  • Anthony Goomba 0

    Great updates, but I’m experiencing the following error in the AppCenter build pipeline:

    MTOUCH : error MT2002: Failed to resolve "Xamarin.Forms.Platform.iOS.EllipseRenderer" reference from "Xamarin.Forms.Platform.iOS,
    • Jennifer Lum 0

      Also getting this error, only from the Android side during compile. Cannot find any info to resolve it

      • xamarinmobile@outlook.com 0

        I am also facing similar issue on Android only…While setting linker option to Link SDk Assemlies…set to none than everything working as expected…

        Did u find any solution for this…

    • Murali Kasalanati 0

      Any luck?,

      I get this on specific project on iOS version. But works on the other sample app.

  • Paul Jackson 0

    Can we extend the Grid Row & Column Definitions to Multibindings as well. ie…

        <MultiBinding StringFormat="{}{0} {1} {2}" Bindings="Employee1.Forename, Employee1.MiddleName, Employee1.Surname" />

Feedback usabilla icon