Bug 45819 - enabling "link all assemblies" in IOS project using XAML files with XAMLC enabled causes all my XAML controls to be stripped
Summary: enabling "link all assemblies" in IOS project using XAML files with XAMLC ena...
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.3.3
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Stephane Delcroix
Depends on:
Reported: 2016-10-23 23:44 UTC by philip
Modified: 2017-03-27 16:48 UTC (History)
5 users (show)

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:

Description philip 2016-10-23 23:44:45 UTC
I would expect the linker to not strip controls which are referenced in XAML+XAMLC.  When I create the controls manually in C# code they are not stripped.  As it is, I have to add the [Preserve] attribute to all my controls used only from XAML.

Under Android this works as expected.
Comment 2 Stephane Delcroix 2017-03-27 12:37:57 UTC
I can't reproduce this issue.

Here are the steps I followed:
- Create a new Xamarin.Forms project (Shared Project, but that shouldn't matter)
- enabled XamlCompilation at assembly level
- enabled "Link All" on iOS linker

The project renders fine.

Please provide the simplest project triggering this issue for you.
Comment 3 philip 2017-03-27 14:50:49 UTC
Sorry it's been too long since I filed this.  Maybe the problem was fixed in the meantime and you can close this?
Comment 4 Samantha Houts [MSFT] 2017-03-27 16:48:46 UTC
Thank you, philip. Please reopen the report if you encounter the issue again.