this is the same XAML page as two windows in macOS, and in the left window, for some reason, the CSS gets ignored
Hi all! Is there any understanding already whether or not Xamarin Mac apps will be able to run with CoreCLR? As far as I know Mono CLR has some special GC features to work with platforms' native API/ABI, so Xamarin Mac apps won't simply work on top of the current CoreCLR despite shared BCL. Am I wrong?
I mean after transition to .NET 5
Both Xamarin.Mac and Xamarin.iOS use runtime features in mono to help track the native object lifetime
Xamarin.iOS on top of that requires AOT, while Xamarin.Mac can be AOT or JIT’ed
Today there is not support for running Xamarin.Mac apps on CoreCLR. There was some community interest and hacking on such an idea in here some months ago
You somehow need to work with the toggleref code, and it gets a tad complicated
Is there a specific runtime feature in CoreCLR you are interested in @GelbChili ?
Or just
dotnet build toolchain?
As noted here (xamarin/xamarin-macios#7528) Xamarin.Mac is moving ot .NET 5 just like Xamarin.iOS, running on top of the “mono side of the runtime house”
That’s a necessary precondition to it running on CoreCLR
:smile:
@chamons We discussed a possibility of creating a game with rich user -scripting capabilities with Xamarin Mac: designing our own script language to hot compile it to IL or make something similar with Lua, etc. So AOT is not an option, and we currently left with JIT or Hybrid mode. Some of us expressed concerns that Mono CLR JIT may not have good enough performance. Since, as far as I know, CoreCLR has much better JIT performance and code quality, if Xamarin Mac after .NET 5 was able to run on top of CoreCLR, it would dismiss such concerns. It's not about tool-chain. Thanks!
I guess, marking
MainScreen with [NullAllowed] would export it as NSScreen? for C# 8?
is there something about CSS styling in the pipeline that works differently than XAML styling? i'm seeing a bug where a stylesheet isn't applied in some cases, but XAML is, and i'm not really sure how to break it down into a test case
if anyone's wondering, i eventually found the bug (or one of them?), and filed it at xamarin/Xamarin.Forms#10484
which brings me to my next question: is there a way to specify platform-specific CSS? basically, this:
<ContentPage.BackgroundColor>
<OnPlatform x:TypeArguments="Color">
<On Platform="macOS">Transparent</On>
<On Platform="iOS">White</On>
</OnPlatform>
</ContentPage.BackgroundColor>e.g., something like
^contentpage[on-platform=macOS] {
background-color: transparent;
}
if not, should i file that as a feature request?
chucker @chucker shrugs and files
@mandel-macaque the fix for xamarin/xamarin-macios#7456 is probably to remove this line: https://github.com/xamarin/xamarin-macios/blob/f8be1a880251e17ff591a90d35cf1217e95cba7e/src/backgroundtasks.cs#L51
the main problem is to verify the fix
and since we cannot match we are trying to instantiate
BGTask but since it is abstract we can't
@rolfbjarne do I like it.. not really, but is the only way
:confused:
Hi.
Does anybody know how to set up a Xamarin Forms app to run on macOS 10.9?
the system requirements you cite are for Xamarin.Mac, not Xamarin Forms
as your link to
contentViewController shows, that's a new API starting in 10.10. my guess is XF doesn't depend on it too much, so you can probably make a fork and possibly a PR to make it compatible to work without contentViewController, but my money is on it isn't worth it — Xamarin Forms on macOS is in preview, supporting it isn't a high priority, and supporting rather old macOS at this point definitely isn't a priority