5 ms·

Probably for the best - been a VS developer for many, many years, since the first version - but the Mac version was never even close to as good as the Windows v

by ejb999 3y ago

Probably for the best - been a VS developer for many, many years, since the first version - but the Mac version was never even close to as good as the Windows version - as much as I wished it was, as my Mac is my primary machine. They either needed to kill it, or make it at least as good as it was on Windows - guess they decided killing it was easier.

pif 3y ago
> the Mac version was never even close to as good as the Windows version Care to add any detail, and reason?
- TheCleric 3y ago
  It couldn't do a LOT of the same things that the Windows version could do. For me the deal breaker was no SSIS package editing.
- sgjohnson 3y ago
  Because the VS version for macOS is essentially just MonoDevelop.
- chedabob 3y ago
  It shared nothing with Visual Studio apart from the name as it was just a rebrand of MonoDevelop. I tried to use it on a Xamarin project a few years ago, and between the poor autocomplete and frequent crashes, I switched to JetBrains Rider for everything but XAML editing. There were also features that were locked behind a $250/month Enterprise subscription which other IDEs provide for free. https://en.wikipedia.org/wiki/MonoDevelop#Visual_Studio_for_Mac https://en.wikipedia.org/wiki/MonoDevelop#Visual_Studio_for_...
SoftTalker 3y ago
Never really made sense that they offered it at all. The number of .NET shops that have their developers on Macs has got to be quite small.
- jspaetzel 3y ago
  It was an acquisition, came with Xamarin
- whizzter 3y ago
  We've got almost all of our backends on .NET, but for us we have plenty of front-end developers and those who're not really full-stack are on Mac's and Linux. Our modern .NET Core codebases aren't much of an issue (pre core 3.1/5 are tricky without Arm support but those are easy enough to upgrade) but we have a bunch of older Framework codebases that forces them to run Windows VM's. The equation for MS is probably that VSMac was good for those targetting the older .NET systems but with Apple going for ARM it's just too much work to get them decent (and Mono's Framework support didn't seem good enough for even a fairly simple project we tried to get running recently) and with the new C# SDK for VSCode mostly giving parity for newer projects there is fairly little reason to spend any effort on VSMac.
- drunkenmagician 3y ago
  40+ devs at our location, mac + .net core but a mix of VSCode or Rider for IDE.

by ejb999 3y ago

pif 3y ago

> the Mac version was never even close to as good as the Windows version Care to add any detail, and reason?

TheCleric 3y ago
It couldn't do a LOT of the same things that the Windows version could do. For me the deal breaker was no SSIS package editing.
sgjohnson 3y ago
Because the VS version for macOS is essentially just MonoDevelop.
chedabob 3y ago
It shared nothing with Visual Studio apart from the name as it was just a rebrand of MonoDevelop. I tried to use it on a Xamarin project a few years ago, and between the poor autocomplete and frequent crashes, I switched to JetBrains Rider for everything but XAML editing. There were also features that were locked behind a $250/month Enterprise subscription which other IDEs provide for free. https://en.wikipedia.org/wiki/MonoDevelop#Visual_Studio_for_Mac https://en.wikipedia.org/wiki/MonoDevelop#Visual_Studio_for_...

SoftTalker 3y ago

Never really made sense that they offered it at all. The number of .NET shops that have their developers on Macs has got to be quite small.

jspaetzel 3y ago
It was an acquisition, came with Xamarin
whizzter 3y ago
We've got almost all of our backends on .NET, but for us we have plenty of front-end developers and those who're not really full-stack are on Mac's and Linux. Our modern .NET Core codebases aren't much of an issue (pre core 3.1/5 are tricky without Arm support but those are easy enough to upgrade) but we have a bunch of older Framework codebases that forces them to run Windows VM's. The equation for MS is probably that VSMac was good for those targetting the older .NET systems but with Apple going for ARM it's just too much work to get them decent (and Mono's Framework support didn't seem good enough for even a fairly simple project we tried to get running recently) and with the new C# SDK for VSCode mostly giving parity for newer projects there is fairly little reason to spend any effort on VSMac.
drunkenmagician 3y ago
40+ devs at our location, mac + .net core but a mix of VSCode or Rider for IDE.