Apple Silicon (M1 chip) Support in Rider

Jaroslav Klim Have you installed a build from the EAP channel via Toolbox? Or just a regular release (Rider 2021.2.x)? Please share what you have in JetBrains Rider | About JetBrains Rider. 

Jaroslav Klim

Changing MSBuild folder in projects < NET6 horrible idea, because you will lose performance while building solution on arm64 machine.

As i'm writing above in this thread, prefer solution it is add ENV Variable 'DOTNET_ROOT' before running project.

Eluchsingerm you can still use 2021.2.1 M1 (Build 515.5080.71) if you want. You still can download it from https://download.jetbrains.com/rider/JetBrains.Rider-2021.2.1-aarch64.dmg if you lost the copy. 

By the way, could you please create a request here https://youtrack.jetbrains.com/issues/RIDER with more details about the problem you experienced with EAP build? We will much appreciate that. Thanks! 

Has anyone experienced really slow performance when running XUnit tests ?

Running tests on Rider 2021.3 EAP4 on Apple M1 mbp set of tests take ~2 min 30 secs.

But running the same code and tests on an Intel x86 mbp, the same set of tests takes ~ 30 secs

This perf issue makes running Xunit tests locally a huge blocker to following best practice.

regards Matt

Emre Besirik Just now I am solving this problem, for newer projects where can be used .NET 6 I use official way/folder. For .NET 5 and .NET Core 3.1 I use nested x64 folder. In Rider you have to change SDK folder on solution level. But there is still problem with no access to Azure CLI login from older version then .NET 6, I do not know why, maybe Rosseta? I have not found official solution for this :-( Let me know if you will find something. Thank you

Guys, I am about to buy new laptop and need your honest opinion. I am considering MBP M1 (been using windows laptops up to now).

Is this thing ready/usable? I expect it to be buggy at this stage, but is it usable with some workarounds?

Anyone know when shall we see the 2021.3 coming to the stable channel?

And btw, anyone able fix the older .net versions + .net6 working side by side issue on a M1 device? (other then a workaround like unzipping the sdk to a different directory) I mean is there an official solution to this problem?

Ekin 

I meant it was something generic like System or whatever that we already had a using directive for. Basically, We had a `class Foo` and it worked fine, then I guess they introduced a new class Foo in the System namespace in preview 7. Now the compiler wants me to decide which Foo this is.

Such an issue is not related to the SDK version Rider uses as runtime. There might be an issue in code analysis (ReSharper backend language server) since not all new languages features or changes are supported yet.  

So, if you still experience the issue, could you please try reproducing this in a demo solution and share it with us at https://youtrack.jetbrains.com/issues/RIDER?

Alexander Kurakin I used Toolbox App, there is only one choice to download EAP version, it is not recognize m1/intel? So I will reinstall it from your link.

Why I had to install Rosseta with 2021.3 EAP ? It is not native Mac ARM app?

Jaroslav Klim, have you downloaded and installed the macOS ARM64 build?

Alexander Kurakin oh I meant it was something generic like System or whatever that we already had a using directive for. Basically, We had a `class Foo` and it worked fine, then I guess they introduced a new class Foo in the System namespace in preview 7. Now the compiler wants me to decide which Foo this is.

But not Rider because I think it is on preview 4, it is not aware of the SDK change causing this issue further down the road. Does that make sense?

stepan.sanda It is first your 2021.2 EAP install? If you updating from previously version, try to remove ~/Library/Application Support/JetBrains/Rider2021.2 and try it again.

Which dotnet version do you have it?

I'm got 6.0.100-preview.5.21302.13 and Rider EAP5 and 6 works perfectly, but only with .net6.0 projects.

Hello stepan.sanda! Please create a new YouTrack request https://youtrack.jetbrains.com/issues/RIDER and attach the Rider logs from your machine right after the issue happens: https://rider-support.jetbrains.com/hc/en-us/articles/360001079770-How-to-collect-Rider-logs- | `Can't access Help menu, how do I find the log file manually?` section.

Thanks! 

Alexander Kurakin

Does Rider 2021.2 EAP6 "Apple Silicon" Edition work with SDK 6.0.100-preview.6 or it was me who failed to kick it off together?

My combination which works fine (without Debug feature) is Rider 2021.2 EAP6 "Apple Silicon" Edition with 6.0.100-preview.4.21255.9

Hello Amigin,

We are not aware of any critical issues with .NET 6 Preview 6 and Rider "Apple Silicon" Edition. So, it would be cool, if you submit a new request here https://youtrack.jetbrains.com/issues/RIDER and describe the problem in detail. We will have a look at it. 

Thanks! 

I removed .net Preview4 completley (by deleting .dotnet directories  "/usr/local/share/dotnet/sdk" and "~/$home/.dotnet")

Installed Prevew6 + EAP7 - and everything works...

Thank you for your great work:   Rider + M1 = Awesome development environment

Hello Katsuomi! 

Please file a new request on YouTrack with all the details like can Rider itself be started without Unity? 

Thanks! 

Still's happening

Any idea??

Hi Team

I have downloaded the new EAP Rider 2012.2 for Apple Silicon version from the link above.

However when I run it and check Help|About the version info looks identical to the non Apple Silicon version !

JetBrains Rider 2021.2
Build #RD-212.4746.113, built on July 30, 2021
...
Runtime version: 11.0.11+9-b1504.13 aarch64
VM: Dynamic Code Evolution 64-Bit Server VM by JetBrains s.r.o.
macOS 11.5.1
.NET 6.0.0

I am sure I am running the newly installed version, but I am not convinced the newly installed version is the Apple Silicon one.

I have several dotnet SDKs installed all < 6, I am wondering if the installer is seeing these and not installing the EAP Apple Silicon version ?

Dear Matthew,

aarch64 in the version info means the 64-bit extension of the ARM architecture. 

For the Intel chips, you will get x86_64.

Hope it helps! 

Have there been updates to the Apple Silicon build after the new .NET previews, or was that build a one time thing? Based on this article, the build still runs on .NET 6 preview 4, but preview 7 has just been released, so I'm wondering if new builds have been generated and uploaded.

Hello Matheus!

Since opening the early preview channel for the Apple Silicon support, we've already published about 10 Rider builds. 

We've skipped "Preview 5" and "Preview 6" versions of the .NET SDK since there were some newly introduced issues that broke several things in Rider, e.g., the debugger. Right now, we are testing Rider on the .NET 6 Preview 7 build. 

Any chance we can see that preview 7 version soon? :). There are some changes on preview 7 that started depending on.

VsCode works but it is slow, I guess it uses x86 omnisharp? Not sure how Rider handles the language server etc stuff.

Ekin Do you experience any issues witn .NET 6 Preview 7 in the current Rider build? The .NET6-preview4 mentioned in the article is a runtime we use to run Rider itself, it does not affect your applications and projects.

It seems to be working pretty good however I noticed that it did not pick up a name collision we had. I think they added a new class in preview7 in some generic namespace and we had one with the same name, it would not compile on pr7 but Rider had no idea.

Ekin Thanks for the reply! In case you meant "global namespaces" by "generic namespaces", there is a feature request to add proper support for Implicit Namespace Imports and Global Using Statements.

If your issue is not related to that, please submit a request for the support team (the "Submit a request" button at the top of the page) and we will have a look at it. Thanks! 

Ekin, no, the latest available build shouldn't expire since it was build as part of the 2021.2.1 release chain. Please check JetBrains Rider | About JetBrains Rider dialog. There shouldn't be an expiration date. 

Thanks! 

Alexander Kurakin I got an error when download the update and I saw the release note which I think is release note for Intel version ?

Failed to prepare an update: Request failed with status code 403

 

We’ve fixed two issues that prevented debugging Blazor WebAssembly applications (RIDER-65999 and RIDER-66599).
T4 template execution works again on macOS (RIDER-66097).
No more errors on an Average() call being ambiguous between Nullable<float> and Nullable<double> (RSRP-484898) and no more 'The type xxx is defined in an assembly that is not referenced...' error for Unity/Mono projects (RSRP-485467).
You can debug a DLL which is loaded from a stream in an AssemblyLoadContext (RIDER-66244).
The "Run all tests" and "Run selected tests" icons in the Unit Tests Explorer are no longer disabled when you open a test project (RIDER-66137).
Ctrl+Shift+Arrow keys ("Stretch to Right"/"Stretch to Left" actions) no longer resize the dialog instead of text selection (IDEA-267294).

Alexander Kurakin BTW, the page states "Every new build will expire after 30 days" and the current build seems to be created on 30th of July.

Does that mean this build will stop functioning in 2 days? In that case, any new builds in the works? :)