Sebastien Pouliot

@marek-safar here's the binlog for the dotnet version. It comes from `main` (not P4) as this includes the latest (feature switches) changes [build-dotnet.binlog.zip](https://github.com/xamarin/xamarin-macios/files/6367804/build-dotnet.binlog.zip)

Another reason (beside stripping which I have working locally) for the native code to be larger might be related to the lack of the LLVM AOT backend. ``` if ((abi...

> @spouliot from the log there is still one optimization disabled (--disable-opt unusedtypechecks) which I think is worth investigating why. 59cdbc6098 > The linker will treat type checks as a...

Results with the `release/6.0.1xx-preview5` branch, commit ea0097c56837c34a484e06d0abdb2e658ea4556f ## Highlights * [Enabled stripping the native executable](https://github.com/xamarin/xamarin-macios/pull/11378) * [Enabled removal of the static registrar](https://github.com/xamarin/xamarin-macios/pull/11474) * [Removal of additional custom attributes with linker...

@filipnavara I noticed a decrease on `main` (P6) in that file size. Not sure if related to your comment or not.

> Nope, it's still wrong (big) in today's ICU package. Maybe, but I do get a smaller size in `main` than P5 > | icudt.dat | 0 | 1,636,880 |...

@jeromelaban Since [we can _override_](https://github.com/xamarin/xamarin-macios/issues/15677#issuecomment-1220080428) (in the general, not the C#, way) the problematic property then it hints to a bug inside Microsoft's SDK. Kind of weird since it's a...

> Update: requires the static registrar to be enabled (not the default for simulator builds as it impact build times). Filed as https://github.com/xamarin/xamarin-macios/issues/15708 https://github.com/xamarin/xamarin-macios/pull/15712 once merged, should make this easier...

While looking at my PR failures I found out that `SinglelineTextBoxView` was not the only one overriding the `SelectedTextRange` property ``` src/Uno.UI/UI/Xaml/Controls/TextBox/MultilineTextBoxView.iOS.cs: public override UITextRange SelectedTextRange ``` That one likely...

Value? yes, it's not a boolean so there's always value :-) This is not a case where tons of tests are likely to give tons more value. OTOH it's cheap...