Microsoft ends Visual Studio for Mac support on macOS: What do you need to know?

Microsoft has announced the end of support for Visual Studio for Mac (VS Mac) and it is said to be retiring on August 31, 2024. Being a .NET developer myself who uses macOS for development, this decision stings. Visual Studio for Mac, despite all the performance and reliability issues, offered a decent and familiar working environment for building and running .NET apps on macOS. But the question that needs to be asked is: Why did Microsoft pull the plug on VS Mac?

Microsoft’s official statement

With today’s announcement, we’re redirecting our resources and focus to enhance Visual Studio and VS Code, optimizing them for cross-platform development. No new framework, runtime, or language support will be added to Visual Studio for Mac. We will also continue to provide runtime and workload updates so you can continue building and shipping applications built on .NET 6, .NET 7, and the Mono frameworks. While not officially supported, we’ve also enabled rudimentary support for .NET 8 in Visual Studio for Mac for building and debugging applications. 

Why I am not happy with this decision

While Microsoft has its reasons, the loss of Visual Studio for Mac is a blow to the Mac .NET developer community. Here’s why I (and potentially many others) find this decision less than ideal:

• Loss of a Familiar IDE: Visual Studio for Mac offered a traditional IDE experience with built-in project management, debugging tools, and a visual designer. Although I love VS Code, but it’s not an IDE. Migrating these workflows to VS Code is possible using extensions, but it requires significant adjustments and learning new tools. It’s not just about missing features; it’s about the established and efficient workflow being disrupted.
• Uncertainty for Existing Projects: Developers with ongoing projects using Visual Studio for Mac now face the task of transitioning to a new environment. This can be a daunting prospect, potentially introducing compatibility issues and workflow disruptions. Large projects with complex dependencies might require extra time and effort to ensure a smooth transition.
• My love for .NET and MacOS: I love MacOS; it’s way more productive and smooth when compared to Windows. When Microsoft first announced Visual Studio for Mac, I was thrilled. It was like getting the best of both worlds. The building time of apps was way faster on my Apple silicon Mac when compared to a Core i7 Windows machine. This change might push a lot of developers back to Windows, or some developers might switch to other frameworks.

The Road Ahead: Embracing Change and Exploring New Options

The news might be a big blow, but it’s not the end for .NET on Mac. Here’s how we can adapt and move forward:

• Embrace the Power of VS Code: Microsoft is fully committed to supporting VS Code and according to them, it’s the path for cross-platform .NET development. Powerful extensions like the C# Dev Kit extension and various language support extensions can significantly enhance VS Code’s capabilities, bringing it closer to a full-fledged IDE experience. While it might not be a perfect replacement for VS Mac initially, VS Code offers a familiar and customizable environment that can be tailored to your preferences over time.
• Explore Alternative IDE Options: The open-source world offers options like Rider (from JetBrains) and MonoDevelop. These IDEs provide .NET development functionalities and might be worth exploring if you prefer a traditional IDE setup. Trying out these alternatives can help you find an environment that feels most comfortable and efficient for your workflow.
• Stay Hopeful and keep trust in the community: The .NET community is known for its vibrancy and resourcefulness. New tools or initiatives might emerge to fill the gap left by VS Mac. Whether it’s Microsoft refining VS Code’s .NET capabilities or the open-source community stepping up, there’s a good chance that innovative solutions will emerge to address the needs of Mac developers.

What are your thoughts on the end of Visual Studio for Mac support? Share your experiences and preferred solutions for .NET on macOS in the comments below! Let’s keep the conversation going and find the best path forward for .NET developers on Mac.

Also check out my other blog where I discuss about how you can level up your development with some Powerful VS Code Extensions.