Getting Started in C# on a Mac

C# and macOS: A Perfect Match for Cross-Platform Development

At the beginning of the video, Tim clears up a common misconception—that you need the Windows operating system to develop in C#. As Tim states, C# and .NET Core are cross-platform technologies. Whether you're using Linux, Windows, or macOS, you can build and run .NET applications on your device.

Tim sets out to demonstrate how to set up a development environment on macOS using Visual Studio Code, the .NET SDK, and free Microsoft tools.

Downloading and Installing the .NET SDK on macOS

Tim begins with a clean Mac setup—just a fresh macOS install with the Edge browser. At 1:13, he navigates to the official .NET site and selects the correct .NET SDK version for his system—ARM64 Apple Silicon in this case.

After the download, he walks through the installation process: opening the file, following the menu instructions, and completing setup via the system's terminal password prompt. Once installed, the .NET SDK is ready to use for writing and executing C# code.

Tim also points out that with the SDK installed, you could start writing code with a basic text editor. However, for the best experience, he recommends using Visual Studio Code, which is much more suited for professional development.

Installing Visual Studio Code on macOS

At 2:47, Tim visits visualstudio.com, which redirects to Microsoft’s Visual Studio portal. From here, he downloads the macOS universal package of Visual Studio Code—a lightweight yet powerful IDE (technically a code editor, not a full IDE like Visual Studio for Windows).

After downloading the zip file, Tim expands it and drags the Visual Studio Code app into the Applications folder for easy access. Once launched, Tim sets up the default theme and skips optional services like GitHub Copilot.

Installing the C# Dev Kit Extension

Tim moves to the Extensions tab in VS Code at 4:09, where he uses the search bar to locate the official C# Dev Kit. This Microsoft-developed tool equips Visual Studio Code with full support for C# development—everything from IntelliSense to project management and debugging.

Once the extension is installed, users gain access to new project templates and enhanced language support. It effectively transforms VS Code into a full development environment tailored for .NET.

Creating a New .NET Project on macOS

With all tools installed, Tim proceeds to create a new .NET Blazor Web App at 4:45. He highlights that the experience in VS Code on macOS differs from Visual Studio on Windows, but the core functionality remains the same.

Tim selects Blazor Web App from the project types, creates a folder called demos, and then a subfolder named BlazorDemo. He chooses the SLNX format for the solution file—this new option improves solution file handling, especially across platforms.

Users are then presented with multiple project options, such as:

• No authentication

• HTTPS enabled

• Server-side interactivity

• Use of top-level statements

All of these choices are part of a more streamlined experience designed to build modern .NET applications.

Running and Debugging the Application

At 7:01, Tim uses the left-hand menu to navigate to the Run and Debug section. He selects Run C# Blazor Demo, which triggers the dotnet build and launch process. The generated code is compiled, and the application is launched locally over HTTPS.

He’s prompted to allow system-level access for developer certificates—an essential step for secure development. After entering his system password, the app launches in the browser, displaying the default Blazor homepage.

Modifying and Saving Code

To prove that the app is live and fully editable, Tim edits the Homepage component at 7:50. He replaces “Hello, App!” with “Hello, YouTube!” in the string displayed.

Tim reminds macOS users that saving files uses Command + S instead of Control + S, as you'd use on Windows. After re-running the program, the change is visible in the browser, confirming that everything is functioning as expected.

Alternatives and Limitations on macOS

Tim discusses some limitations macOS developers may face at 9:02. While Visual Studio Code with the C# Dev Kit offers strong support, the full Visual Studio IDE isn’t available on macOS due to its deep integration with Windows system libraries.

As an alternative, Tim recommends JetBrains Rider, a cross-platform IDE that supports .NET development on macOS and Linux. It’s free for personal use in many cases and offers a rich, professional experience.

Project Types That Won’t Run on macOS

At 10:22, Tim cautions that some project types won’t run on macOS due to dependencies on Windows DLLs. Specifically, the following are not supported:

• WinForms

• WPF

• UWP (Universal Windows Platform)

These Windows-based applications rely on UI rendering libraries exclusive to the Windows operating system. While you might technically write code for them, you won’t be able to execute or debug the app on a Mac.

However, most other .NET project types are fully supported on macOS, including:

• ASP.NET Core

• Razor Pages

• Web APIs

• Blazor Server

• Blazor WebAssembly

• Console applications

Final Thoughts: macOS is Ready for .NET Development

Tim wraps up at 11:01, emphasizing that macOS users have full access to C# development tools—all free, official, and well-supported by Microsoft. Whether you're building a web app, a console project, or an API, the macOS environment is fully capable with .NET SDK, Visual Studio Code, and the C# Dev Kit.

He also hints at future videos covering JetBrains Rider and Linux setups, underlining the full flexibility of the .NET ecosystem across platforms.

Conclusion

Thanks to tools like Visual Studio Code, the .NET SDK, and the C# Dev Kit, C# development on macOS is accessible, flexible, and robust. As demonstrated by Tim Corey in his video, getting started is straightforward and free—and it's a great way for developers to build modern applications across platforms.

If you're a macOS user looking to dive into .NET, now’s the time to get started.