title: Bindable property at ContentPage level
body: <p>I have a ContentPage where I've created a bindable property, so that I can pass some info from the ViewModel to the class that implements the ContentPage.</p>
  
  <p>To make it clearer, the code behind class has new bindable property (ConnectionSettingsEnabled) defined:</p>
  
  <pre><code>public partial class ConnectionSettingsPage : ContentPage
  {
      public static readonly BindableProperty ConnectionSettingsEnabledProperty = BindableProperty.Create(nameof(ConnectionSettingsEnabled), typeof(bool), typeof(ConnectionSettingsPage), true, propertyChanged: HandleConnectionSettingsEnabledChanged);
      public bool ConnectionSettingsEnabled
      {
          get { return (bool)GetValue(ConnectionSettingsEnabledProperty); }
          set { SetValue(ConnectionSettingsEnabledProperty, value); }
      }
  
      (... a bit more code...)
  }
  </code></pre>
  
  <p>And the XAML has this code:</p>
  
  <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;ContentPage xmlns="http://xamarin.com/schemas/2014/forms" 
           xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
           x:Class="MyProject.Pages.Settings.ConnectionSettingsPage"
           Title="{me:TranslateExtension Text=Server}"
           ConnectionSettingsEnabled="{Binding IsConnectionInfoEditable}"&gt;
  </code></pre>
  
  <p>All was well and working, but I've just upgraded to VS8.2 for macOS, and now the new editor (VS for macOS has finally replaced their horrible XAML editor with the same engine as VS for Windows) complains about the fact that the <em>property ConnectionSettingsEnabled was not found in type ContentPage</em> (which actually makes sense, once you think about it).</p>
  
  <p>The weird thing is that everything compiles and works perfectly, but I can't escape the feeling that this is not the proper way to implement what I wanted.</p>
  
  <p>Anyone has an example of what would be the proper way to implement a bindable property for a single ContentPage and reference it in its XAML?</p>