Bug 53198 - XAMLC error: Missing Value for Setter
Summary: XAMLC error: Missing Value for Setter
Status: RESOLVED DUPLICATE of bug 52622
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-09 17:06 UTC by adamhewitt
Modified: 2017-03-09 20:53 UTC (History)
2 users (show)

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


Attachments
Reproduction project (1.64 KB, application/x-zip-compressed)
2017-03-09 17:06 UTC, adamhewitt
Details


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 DUPLICATE of bug 52622

Description adamhewitt 2017-03-09 17:06:30 UTC
Created attachment 20251 [details]
Reproduction project

This DOES NOT fail on 2.3.3.180. Using the property syntax of a Style Setter fails XAMLC.

<Style TargetType="StackLayout">
  <Setter Property="HeightRequest">
    <Setter.Value>
      <OnPlatform x:TypeArguments="x:Double" iOS="44" Android="60" />
    </Setter.Value>
  </Setter>
</Style>


The reproduction project is a VS2017 multi-target project, but I would expect the same failure with an older project type.
Comment 1 Samantha Houts [MSFT] 2017-03-09 18:44:50 UTC

*** This bug has been marked as a duplicate of bug 52622 ***
Comment 2 adamhewitt 2017-03-09 20:13:18 UTC
Thanks, glad to know that's fixed. Since that's a private bug can you tell me if there's an expected ship of the fix?

Also, I realize people could put confidential things in issue titles, but it might be helpful to have titles *always* visible. Mainly, enough information to help reporters (me) recognize a duplicate without exposing contents in order to save you time.
Comment 3 Samantha Houts [MSFT] 2017-03-09 20:53:46 UTC
Good feedback! I agree. :)

The fix is bundled in 2.3.4-pre3, which should be shipping any day now.

Thanks again for the report!