Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xamarin.Mac supports .Net Standard 2.0 #3555

Merged
merged 1 commit into from
Apr 15, 2019

Conversation

sergey-tihon
Copy link
Member

fix for #3500

@forki
Copy link
Member

forki commented Apr 15, 2019 via email

@matthid
Copy link
Member

matthid commented Apr 15, 2019

How does that fit into the table at the end of this document?

@sergey-tihon
Copy link
Member Author

@forki I cannot find info about 2.1 except this:

.NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1.

I assume that it is not released yet.

@matthid at least based on this table, it is supported
_NET_Standard___Microsoft_Docs

BTH the difference between Modern & Full version of Xamarin.Mac still not clear for me
Fullscreen_4_15_19__10_13_AM
Fullscreen_4_15_19__10_14_AM

@matthid
Copy link
Member

matthid commented Apr 15, 2019

Question is how do they differ in the NuGet package. Maybe they have different monikers or the moniker is versioned now?
What about people using older versions of Xamarin and a newer version of Paket (including this PR). That will lead to issues, correct? Or are all Xamarin users forced to use latest somehow?

@forki
Copy link
Member

forki commented Apr 15, 2019

yeah it's weird that they only have one moniker. that's nuts

@sergey-tihon
Copy link
Member Author

I have no idea, tbh, I think depends on the IDE version that you have (latest available at the install time). I just know that latest Paket generate incorrect assembly references nowadays.

Do you know Xamarin expert that can consult us ? // cc @TimLariviere

@forki forki merged commit 1d48b32 into fsprojects:master Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants