xamarin/xamarin-macios

See https://aka.ms/dotnet-discord for our primary community location.

Chris Hamons

@chamons

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?

Sebastien Pouliot

@spouliot

fwiw XM-on-coreclr will be much easier after .net5 is out, if you wish to help make it happen :smile:

Sören Nils Kuklau

@chucker

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

so Xamarin Mac isn't moving to .NET 5 at all? or .NET 5, but only with Mono's AOT runtime?

Chris Hamons

@chamons

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

Sören Nils Kuklau

@chucker

(I can't speak for @GlebChili, but personally, I'm actually most interested in the more modern csproj format. Call me vain. :) )

Chris Hamons

@chamons

Short form csproj will be supported in the .NET 5 release for sure

:smile:

Sören Nils Kuklau

@chucker

Gleb Krasilich

@GlebChili

@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!

Csaba8472

@Csaba8472

hello is there a way to create watchos binding library in visual studio for mac? I'd like to bind a watch os framework in my watch os project but I can't do it without a watchos binding project. Thank you!

Tomáš Linhart

@TomasLinhart

Hi, where are the system bindings defined? I tried to search for it on GitHub and I was unable to find it. For instance, NSScreen.MainScreen is not defined as nullable but it can be null based on Swift interface.

Sören Nils Kuklau

@chucker

Think you mean https://github.com/xamarin/xamarin-macios/blob/0cab45b7995b1b34ad1fc76886afd49ff5aff284/src/appkit.cs#L13081

Tomáš Linhart

@TomasLinhart

@chucker Yes, thank you. GitHub search didn't include the file in results, maybe it is too big. Anyway, is is there way to mark things as nullable? I don't see any nullable annotations there. Except of [NullAllowed].

I guess, marking MainScreen with [NullAllowed] would export it as NSScreen? for C# 8?

Rolf Bjarne Kvinge

@rolfbjarne

yes, [NullAllowed] will make the generated code accept nulls. We're working on generating the nullable annotations too, but that's still work in progress.

Tomáš Linhart

@TomasLinhart

this is only getter so there is not accepting, it is only returns

Rolf Bjarne Kvinge

@rolfbjarne

then the generated code wouldn't change, it may still return null

Sebastien Pouliot

@spouliot

nullability progress is tracked in xamarin/xamarin-macios#6154

Sebastien Pouliot

@spouliot

I just updated the issue, to answer the last question.

Sören Nils Kuklau

@chucker

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

Sebastien Pouliot

@spouliot

here might not be the best place to ask about XAML :smile: or even XF - we know what it is but it’s not our area of expertise

Sören Nils Kuklau

@chucker

oh right, this isn't XF. sorry!

Sebastien Pouliot

@spouliot

np :smile:

Rolf Bjarne Kvinge

@rolfbjarne

@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

Alex Soto

@dalexsoto

Yep we discussed that yesterday, Apple is very likely returning a custom subclass

and since we cannot match we are trying to instantiate BGTask but since it is abstract we can't

Rolf Bjarne Kvinge

@rolfbjarne

yep, exactly

Manuel de la Pena

@mandel-macaque

@rolfbjarne that is the conclusion we arrived

@rolfbjarne do I like it.. not really, but is the only way

:confused:

Julio César Rocha

@JunielKatarn

Hi.
Does anybody know how to set up a Xamarin Forms app to run on macOS 10.9?

xamarin/xamarin-macios#8556

Sören Nils Kuklau

@chucker

XF is barely running on modern macOS, let alone a release that's seven years old

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

Julio César Rocha

@JunielKatarn

That's too bad. I hope the XF team will at least acknowledge this and state the minimum supported version clearly.
That said, I tried my app in macOS 10.10, and it still crashes, but the offending selector IS supported in that version.

I'll follow up in a new GitHub issue.

Sören Nils Kuklau

@chucker

state the minimum supported version clearly

XF on macOS isn’t supported at all; it’s in preview.

Julio César Rocha

@JunielKatarn

Yeah, I should have said "current targeted".

Sören Nils Kuklau

@chucker

Hm, yeah, https://github.com/xamarin/Xamarin.Forms/wiki/Platform-Support should list per-platform requirements and doesn’t

Julio César Rocha

@JunielKatarn

Neither does the per-platform "Report".
I did find something useful in the .NET AppKit docs:
https://docs.microsoft.com/en-us/dotnet/api/appkit.nssplitviewitem.minimumthickness?view=xamarin-mac-sdk-14

There seems to be an annotation declaring the supported OS version explicitly.

Do you know who owns the AppKit .NET projection, and specifically, the ObjCRuntime types?

Rolf Bjarne Kvinge

@rolfbjarne

For issues with the AppKit bindings, or in the ObjCRuntime namespace, you can file bugs in https://github.com/xamarin/xamarin-macios/issues

gonzobrains

@gonzobrains

Hi. First time visitor here. I'm dead in the water with trying to open storyboards right now. Originally my error was due to the render timing out. I upgraded to VS 2019 and now I get

"An error occurred while initializing the frame's content
System.ArgumentException: 'ZoomMenu_100 ' is not a valid value for property 'Name'."

I upgraded to VS 2019 Preview (which is supposed to fix this) but still get the error. What can I do now?

Where communities thrive

People

Repo info

Activity