Bug 43450 - Faulty syntax of Grid.RowDefinition wasn't caught with XamlC & doesn't generate run-time error
Summary: Faulty syntax of Grid.RowDefinition wasn't caught with XamlC & doesn't genera...
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-08-17 08:14 UTC by Frankie Foo
Modified: 2016-09-22 14:14 UTC (History)
3 users (show)

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

XF project to demonstrate the bug (199.95 KB, application/octet-stream)
2016-08-18 01:29 UTC, Frankie Foo

Description Frankie Foo 2016-08-17 08:14:27 UTC
        <RowDefinition Height="*"/>

<Grid.RowDefinition> is a faulty syntax.

Without XamlC turn on, the code above can be build but will encounter run-time error, with the error will state that RowDefiniton is not a property of grid.

With XamlC turn on, the code above can be build, and will not encounter run time error.
Instead the grid itself will generate the rows automatically (based on the children).
Comment 1 Samantha Houts [MSFT] 2016-08-17 18:24:22 UTC
Using the above code with XamlC enabled, I get:

Error	Position 7:5. No property, bindable property, or event found for 'RowDefinition'

If you could please attach a reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue, we would very much appreciate it.  

For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d  

Warm regards, 
Xamarin Forms Team
Comment 2 Frankie Foo 2016-08-18 01:29:11 UTC
Created attachment 17097 [details]
XF project to demonstrate the bug
Comment 3 Samantha Houts [MSFT] 2016-08-18 22:29:46 UTC
Thank you! We'll look into this further.
Comment 4 Samantha Houts [MSFT] 2016-09-12 18:31:16 UTC
Should be fixed in 2.3.3-pre1. Thank you!
Comment 5 Parmendra Kumar 2016-09-22 14:14:02 UTC
I have checked this issue with Forms version and observed that this issue has been fixed.

Hence closing this issue.


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