-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Question: support for macOS on ARM #4879
Comments
cc @richlander who was asking for user input for platform support at https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-6/ |
Adding @leecow as well |
Yes, we will support .NET Core on the new Mac hardware. |
Little bit more context: https://twitter.com/runfaster2000/status/1279821716944900096 We are still working through this, so we don't have anything like release dates to share yet. |
Hey is there any update on this? |
With the M1 chip being announced today is there any additional information available? |
Just ordered the new macbook pro with apple silicone, cant wait to develop .NET Core using Visual Studio Code |
Any road map about that ? I think MSFT need to add .NET 6 preview asap , I need this to build MAUI in my new apple silicon mbp |
Plan:
Tracking issue for M1 enablement: dotnet/runtime#43313. I asked for a tracking issue for Rosetta 2. |
Rosetta 2 tracking issue: dotnet/runtime#44897 |
I tested it. |
Hi @richlander |
I'm curious as to why this issue is closed? Has it been resolved? |
@richlander has listed the tracking issues for this work above. |
Is there any update on this? I am trying to install the msteams vscode extension on m1 mac but its pinned at SDK 3.1 Will SDK 3.1 have patches to support m1 or allow rosetta to emulate it? |
Hi!
Are you planning .Net Core (or unified .Net) to support the upcoming ARM (Apple Silicon) based Macs?
I know its a huge effort, but many developers are counting on you. .Net core was intended to be a multiplatform solution, so I expect it to be supported in a future release (maybe .Net 6?).
Thanks.
The text was updated successfully, but these errors were encountered: