Bug 44216 - No property, bindable property, or event found when using xamlc
Summary: No property, bindable property, or event found when using xamlc
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-09-12 19:07 UTC by nicollas braga
Modified: 2017-06-13 14:50 UTC (History)
5 users (show)

See Also:
Tags: ac
Is this bug a regression?: ---
Last known good build:

No property or bindable property not found for FontSize when enable XamlC compilation (270.47 KB, application/x-zip-compressed)
2017-06-13 12:04 UTC, Magesh Kumar

Description nicollas braga 2016-09-12 19:07:10 UTC
I've create an Behavior, its compile and run without any problem when using the default xaml

but wen you try to use the xamlc ([assembly: XamlCompilation(XamlCompilationOptions.Compile)]) 

its don't compile with error Position 13:72. No property, bindable property, or event found for 'MinLengh'

<?xml version="1.0" encoding="utf-8" ?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
      <StackLayout VerticalOptions="CenterAndExpand" Padding="5,0,0,5">
        <Label Text="Cdade" />
        <Entry x:Name="cidade" Placeholder="Cidade - UF" >
            <Controls:RequiredBehavior x:Name="cidadeRequiredBehavior" MinLengh="5"/>

 public class RequiredBehavior : Behavior<Entry>
        static readonly BindablePropertyKey IsValidPropertyKey = BindableProperty.CreateReadOnly("IsValid", typeof(bool), typeof(ComparisonBehavior), false);
        public static readonly BindableProperty IsValidProperty = IsValidPropertyKey.BindableProperty;
        static readonly BindableProperty MinLenghProperty = BindableProperty.Create("MinLengh", typeof(int), typeof(ComparisonBehavior), 1);
        static readonly BindableProperty MaxLenghProperty = BindableProperty.Create("MaxLengh", typeof(int), typeof(ComparisonBehavior), int.MaxValue);

        /// <summary>
        /// Get the value that determine if the value has validated
        /// </summary>
        public bool IsValid
            get { return (bool)base.GetValue(IsValidProperty); }
            private set { base.SetValue(IsValidPropertyKey, value); }

        /// <summary>
        /// Get or Set the min lengh 
        /// </summary>
        public int MinLengh
            get { return (int)base.GetValue(MinLenghProperty); }
            private set { base.SetValue(MinLenghProperty, value > 0 ? value: 1); }

        /// <summary>
        /// Get or Set the max lengh 
        /// </summary>
        public int MaxLengh
            get { return (int)base.GetValue(MaxLenghProperty); }
            private set { base.SetValue(MaxLenghProperty, value > 0 ? value: 1); }
Comment 1 Stephane Delcroix 2017-01-25 13:49:37 UTC
You're not going to like it, but XamlC is right in failing, and the normal parser should fail as well for the following reason:
 - the BindableProperty MinLengh is private,
 - the setter for the MinLengh property is private as well.

Here's the fix that will make it fail all the time https://github.com/xamarin/Xamarin.Forms/pull/717
Comment 2 Stephane Delcroix 2017-02-02 14:35:12 UTC
this will be fixed in 2.3.5-pre1
Comment 3 Magesh Kumar 2017-06-13 12:04:05 UTC
Created attachment 22853 [details]
No property or bindable property not found for FontSize when enable XamlC compilation
Comment 4 Magesh Kumar 2017-06-13 12:07:51 UTC
This issue still exists in version. Attached a sample (FontSizeSample) which replicates issue. 

Attached in previous update.
Comment 5 Stephane Delcroix 2017-06-13 14:10:54 UTC
@Magesh: the message you're reporting is unrelated to this issue.

You're complaining that this syntax

    <Font FontSize="20"/>


    ./FontSizeSample/Page1.xaml(13,13): Error: Position 8:13. No property, bindable property, or event found for 'FontSize', or mismatching type between value and property. (FontSizeSample)

which is totally to be expected, as Font.FontSize doesn't define any public setter. The message could be slightly more clear if it was saying "No accessible property setter, ..." But I'm quite sure you get the idea without the more verbose language.
Comment 6 FieldstrikeMobile 2017-06-13 14:15:24 UTC
I was sent here by Syncfusion because their documentation states to use it like so:  https://help.syncfusion.com/xamarin/sfchart/datamarker#customizing-labels

<chart:DataMarkerLabelStyle TextColor="Blue" BorderColor="Red" BorderThickness="2" BackgroundColor="Aqua" Angle="315" Margin="5">
              <Font FontSize="18" FontAttributes="Italic"/>

perhaps the way they are advising customers to set Font is incorrect?
Comment 7 Stephane Delcroix 2017-06-13 14:37:26 UTC
> perhaps the way they are advising customers to set Font is incorrect?

Comment 8 FieldstrikeMobile 2017-06-13 14:38:55 UTC
How would you advise setting the font in the case above?

I had to extend DataMarkerLabelStyle and Set the font in code. Felt messy
Comment 9 Stephane Delcroix 2017-06-13 14:48:32 UTC
I'd do

    <chart:DataMarkerLabelStyle Font="Italic,42" />
Comment 10 Stephane Delcroix 2017-06-13 14:49:41 UTC
see https://github.com/xamarin/Xamarin.Forms/blob/master/Xamarin.Forms.Core/FontTypeConverter.cs#L12 for references on how to use the Font Type Converter
Comment 11 FieldstrikeMobile 2017-06-13 14:50:44 UTC
Brilliant! thanks

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.