Ask HN: Is doing .NET development on a Mac viable today?

I develop on macOS with my iMac. I’ve done some freelancing with ASP .Net Core and lots of side projects. Currently, I’m working on a Maui app that is iOS specific.

Using the terminal with dontnet Cli and vim is fantastic.

The Maui ecosystem is new, so there is that and my iMac is Intel.

No idea these days, but @praeclarum was a pretty big c# / mono evangelist on Mac several years ago.

I've been developing an ASP.Net Core Web Api on Linux for the last few months with the dotnet CLI and I haven't run into any cross platform issues yet.

I've used both VSCode and Rider and I think both provide an enjoyable development experience.

Aside from VS only running on Windows, it doesn't feel like a second class experience at all to me.

I've been spending a lot of time writing web apps with ASP.NET Core on my Mac with Rider this summer. It has generally been an excellent experience, with one minor caveat.

Debugging ASP.NET integration tests has worked far better on Rider than it does on my VS2022 instance on Windows - where I have to manually trigger the debugger within the test itself. On Rider it worked as expected from the get-go.

You may run into some issues if your project depends on private NuGet feeds, primarily hosted by Azure DevOps. Rider fails to authenticate with ADO no matter what I do, so I had to fall back on manually installing those packages with the dotnet utility.

On small, focused code bases, yes. Anything built in the last 5 years or so can probably be made to work with .NET core and on a non-windows machine.

On large monolithic .NET codebases originally built from the 2000s era, absolutely not. You need to either rewrite or stick to Windows. Porting doesn't seem to be worth the effort.

We (telepathy labs) have our entire platform built in .net core. Most engineers are using macbook pros with a mix of Rider / vs studio ma for ide). The only real issue has been nuget packages with amd64 only binaries bundled in (I’m looking at you librdkafka). You can usually work around theses sort of issues though. Overall its certainly a productive and stable environment, for us at least.

Our whole team does .NET development using VSCode on M1 MacBooks. Our primary API is C# / .NET Core & front end clients are all in React / React Native. We love it.

No friction points that I can think of off the top of my head. Biggest upside is that it just works seamlessly. When switching between code bases, pulling PR’s for review, etc. it’s quite nice not worry about things like whether you have access to the iOS emulator.

I develop `tone`[1] and `tonehub`[2] (command line app and web api) completely on a 2015 MacBook Pro using Rider and I love it so far. I may not be the most experienced .NET developer, but this might be good as another perspective... It's easy and very intuitive. Deployment is also very simple (manually as well as via github actions)

[1]: https://github.com/sandreas/tone

[2]: https://github.com/sandreas/tonehub

With tree shaking .NET you can compile your C#/NET program into a fairly small single executable on the three major platforms if that's what you need, which is nice.

Generally fantastic, will second comments on web development being pain free.

Probably want to invest in Rider, I seldom here good things about VSCode and VS for Mac(it’s a unique program, not full visual studio like the name suggests).

Have had some hiccups:

For desktop development I have a little app to run a label printer, Avalonia itself ported over fairly seamlessly however I discovered printing (system.drawing in general) is windows only.

Not .Net specific but I’ve had problems with emulation.

MSSQL docker isn’t supported, you can use edge which has some limitations which may or may not be a problem (or not a problem till it is).

Azurite docker works but needs Rosetta.

CosmosDB emulator flat out doesn’t work.

I'm on m1 MacBook and do xamarin and c# projects all day full time.

Rider is really nice and I now find going back to VS harder as everyday passes.

It is. We have many developers doing this at my company, full-time. They use Parallels to run the apps we have that require .NET Framework, but mainly work on .NET Core 3.1 and newer apps using M1 Macs.

There were some hurdles to jump over initially, but our internal tooling is evolving and it's a very viable option for us now.

We do a lot of .net core development (our main product is a large codebase in .net with code written and refactored from back to 2013) and most of it is on mac. Most use rider or vs for Mac. Most code is asp.net core, we have a large xamarin app and a few internal desktop apps (written in windows.forms which work under mac, windows and linux). I would say the experience is great.

I’m using a (M1) mac to write F# in Rider - no issues at all.

“As a client, not being able to make encrypted connections to TLS 1.3-only services/servers is by far the bigger issue.”

https://github.com/dotnet/runtime/issues/1979

Doing .net 6 development on Xubuntu + Rider, and it's wonderful. Everything works apart from the profiler, for some reason. I also miss LinqPad a lot. Rider has "C# interactive", but it can be difficult to set up when you need custom .dlls etc. Generally the abscence of all of the Windows bloat and Docker/bash/console workarounds/stubs and so on, you get the idea, is a bliss.