Bug 53833 - Exception when create a BindableProperty with an (invalid) default value.
Summary: Exception when create a BindableProperty with an (invalid) default value.
Status: RESOLVED ANSWERED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-03-23 07:59 UTC by Ton Snoei
Modified: 2017-03-29 15:27 UTC (History)
2 users (show)

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

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

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.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description Ton Snoei 2017-03-23 07:59:45 UTC
The code below is working well:

public static readonly BindableProperty MinValueProperty = BindableProperty.Create(nameof(MinValue), typeof(double), typeof(Bar), 0d);

However, the code below results in a TypeException:

public static readonly BindableProperty MinValueProperty = BindableProperty.Create(nameof(MinValue), typeof(double), typeof(Bar), 0);

Finding problems like this is really annoying and time consuming. Why not just ignoring wrong defaults and, when possible, convert it to the correct type?
Comment 1 Paul DiPietro [MSFT] 2017-03-29 15:27:51 UTC
After some brief discussion, we concluded that this sort of magic conversion to the correct type is not handled which is why the exception is explicitly thrown, and would not expect this to be changed.