4 ms·

True as long as you're not on an M1 Mac; right now it's a little bit of a mess since .NET 5.0 isn't fully supported and .NET 6.0 isn't quite ready for primetime

by evo_9 5y ago

True as long as you're not on an M1 Mac; right now it's a little bit of a mess since .NET 5.0 isn't fully supported and .NET 6.0 isn't quite ready for primetime (this release gets us a ton closer though). It's still doable, but with limitations; that said I still love my m1 air and .NET 6 will make it that much better/easier to do dev on it when it drops this Fall. But yeah, it's a great time for sure, just good to keep that in mind since you also can't run any of MS's (or JetBrains) IDE's (or MS SQL) on a VM in Win10 ARM. Win10ARM VM does smoke though so hopefully they releases all that on ARM, that would another nice option.

abdusco 5y ago
JetBrains has released a preview version of Rider that works reasonably well on M1. It is still buggy, but editor & IDE experience is good enough. https://rider-support.jetbrains.com/hc/en-us/articles/4401925025810 https://rider-support.jetbrains.com/hc/en-us/articles/440192...
- evo_9 5y ago
  It's not an IDE issue; .Net 5.0 doesn't fully run on M1, aka you can't connect to the debugger and step into the code, among other things. VS Code is native on M1, and Visual Studio for Mac also runs via Rosetta2 (but I don't run it). Did not know that about Rider, thx I'll def check it out.
  - abdusco 5y ago
    I can run and debug .NET 5 apps (on Rosetta) using both VS Code & JetBrains Rider. You might have to update .NET 5 SDK to a more recent version.
immutology 5y ago
I run and develop on the x64 versions of dotnet core 3.1 and dotnet 5 on my M1 Macbook Air every day and don't have problems. It runs via Rosetta 2 translation, and probably isn't as fast or memory efficient as it could be, but I don't have major issues and it runs a lot faster and keeps my mac cooler than if I try to run in Windows on ARM in Parallels. I use VS for Mac 2019 (x64) and VS Code (arm64) for development work on a near daily basis. That said, I tried installing the arm64 dotnet 6 preview and it broke the x64 versions I had installed and although I could debug/attach in VS Code, I could not get it to debug in VS for Mac 2019. From what I understand, the issue is that the dotnet binary for x64 got replaced with the arm64 one. There is only one on the system at a time and the arm64 version doesn't know how to work with the x64 architecture sdks/runtime. There is some discussion and links to related issues in this GH issue: https://github.com/dotnet/sdk/issues/16896 https://github.com/dotnet/sdk/issues/16896 Regarding SQL, I use the Docker Azure SQL Edge arm64 image and it works okay for most thing but doesn't support some of the more advanced features like full text search or spatial types. For Database Projects (dacpac), Azure Data Studio with the Database Projects extension works okay for basic editing and deployment. However, it's not nearly as complete or refined as the database project edit/deploy experience in the Windows version of VS 2019. As far as I can tell it doesn't create new refactorlog entries for renamed objects and I can't figure out how to create a new deployment profile so I have to select the database connection every time I deploy. I have been running the x64 build of dotnet 6 preview 4 and now preview 5 for a while and have not many issues. One thing that happened is that it broke the dacpac deploy in Azure Data Studio but there was a relatively simple workaround -- added a configuration setting in Azure Data Studio to override the dotnet SDK path to point to a folder where I had put dotnet 5.

by evo_9 5y ago

abdusco 5y ago

JetBrains has released a preview version of Rider that works reasonably well on M1. It is still buggy, but editor & IDE experience is good enough. https://rider-support.jetbrains.com/hc/en-us/articles/4401925025810 https://rider-support.jetbrains.com/hc/en-us/articles/440192...

evo_9 5y ago
It's not an IDE issue; .Net 5.0 doesn't fully run on M1, aka you can't connect to the debugger and step into the code, among other things. VS Code is native on M1, and Visual Studio for Mac also runs via Rosetta2 (but I don't run it). Did not know that about Rider, thx I'll def check it out.
- abdusco 5y ago
  I can run and debug .NET 5 apps (on Rosetta) using both VS Code & JetBrains Rider. You might have to update .NET 5 SDK to a more recent version.

immutology 5y ago

I run and develop on the x64 versions of dotnet core 3.1 and dotnet 5 on my M1 Macbook Air every day and don't have problems. It runs via Rosetta 2 translation, and probably isn't as fast or memory efficient as it could be, but I don't have major issues and it runs a lot faster and keeps my mac cooler than if I try to run in Windows on ARM in Parallels. I use VS for Mac 2019 (x64) and VS Code (arm64) for development work on a near daily basis. That said, I tried installing the arm64 dotnet 6 preview and it broke the x64 versions I had installed and although I could debug/attach in VS Code, I could not get it to debug in VS for Mac 2019. From what I understand, the issue is that the dotnet binary for x64 got replaced with the arm64 one. There is only one on the system at a time and the arm64 version doesn't know how to work with the x64 architecture sdks/runtime. There is some discussion and links to related issues in this GH issue: https://github.com/dotnet/sdk/issues/16896 https://github.com/dotnet/sdk/issues/16896 Regarding SQL, I use the Docker Azure SQL Edge arm64 image and it works okay for most thing but doesn't support some of the more advanced features like full text search or spatial types. For Database Projects (dacpac), Azure Data Studio with the Database Projects extension works okay for basic editing and deployment. However, it's not nearly as complete or refined as the database project edit/deploy experience in the Windows version of VS 2019. As far as I can tell it doesn't create new refactorlog entries for renamed objects and I can't figure out how to create a new deployment profile so I have to select the database connection every time I deploy. I have been running the x64 build of dotnet 6 preview 4 and now preview 5 for a while and have not many issues. One thing that happened is that it broke the dacpac deploy in Azure Data Studio but there was a relatively simple workaround -- added a configuration setting in Azure Data Studio to override the dotnet SDK path to point to a folder where I had put dotnet 5.