Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Using the XAML compiler on attributes with multiple values fails (only tested on absolute layout):
<BoxView BackgroundColor="Gray" AbsoluteLayout.LayoutBounds="0,0,1,100"
gives an error that enum is not defined for the multiple values of layout flags:
Error: Position 14:16. Enum value not found for XProportional,YProportional,WidthProportional
I think we solved this one already... checking
I too ran into this issue with the following xaml:
<BoxView Color="Fuchsia" AbsoluteLayout.LayoutFlags="PositionProportional" AbsoluteLayout.LayoutBounds="0.5,0.5,40,40" />
As a work around you can switch from attribute syntax to element syntax. This provides type knowledge so that the Xaml compiler can create the correct type. In attribute syntax, when the Xaml is interpreted at run-time, it relies on the type converter to translate the string to the desired type.
Something like this:
<BoxView Color="Fuchsia" AbsoluteLayout.LayoutFlags="PositionProportional">
<Rectangle X="0.5" Y="0.5" Height="40" Width="40" />
I have tried to reproduce this issue but not able to reproduce this issue. I have followed the code provided in bug description and comment #2 and after using these code my app deploy successfully on device,
Please follow the screencast and let me know If I have missed anything to reproduce this issue.
Microsoft Visual Studio Professional 2013
Version 12.0.30723.00 Update 3
Microsoft .NET Framework
Installed Version: Professional
Xamarin 188.8.131.52 (21aad62)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 184.108.40.206 (50280e4)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 220.127.116.11 (122b860)
Visual Studio extension to enable development for Xamarin.iOS.
Xamarin.iOS Unified Migration 1.0
Automated migration for Xamarin iOS Classic projects to Unified
Thank you for looking at this. After a full clean and recompile the code I posted in comment #2 appears to be working. Sorry for any inconvenience.
As per comment #4 closing this issue.
@abel, Could you please check this issue with latest forms version or clean the solution and please feel free to reopen this issue if you getting same issue as mentioned in bug description.
Yes.Thanks...Looks it is working...I cannot understand what I was doing wrong...Or there were some old files not properly compiled.
Maybe I was using an old version on Forms...
As per comment #6 and comment #7, I am closing this issue.