.NET SDK

.NET SDK provides command-line tools, compilers, templates and build infrastructure for developing .NET applications and libraries. It serves C#, F# and other .NET developers building console applications, web services and supported platform-specific projects. The SDK includes the .NET Runtime and ASP.NET Core Runtime for its own release; it is more than a runtime-only installer.

Features

• Create projects with templates and build them through the dotnet CLI and MSBuild.
• Restore NuGet packages, run applications and execute supported tests.
• Publish applications for supported deployment targets.
• Work with C#, F# and compatible editors and IDEs.
• Select installed SDKs for projects through global.json and inspect installed SDK/runtime versions.
• Add optional workloads and tools for specific development scenarios.

Mac installation and first use

Install brew install --cask dotnet-sdk. Homebrew selects the Arm64 PKG on Apple Silicon and x64 PKG on Intel and exposes dotnet and dnx command links. The Microsoft installer can also be downloaded and opened directly. Reopen Terminal if the command is not available after installation. Check dotnet --info, dotnet --list-sdks and dotnet --list-runtimes. For a first console project, use dotnet new console -o HelloWorld, change to its directory and run dotnet run. A project global.json can select a different SDK than the newest installed one. This command-line toolkit does not install a general-purpose standalone Mac GUI or IDE.

Requirements, dependencies and support

The current package is SDK 10.0.401, paired with .NET/ASP.NET Core runtime 10.0.12. The Homebrew cask declares macOS >=12 and Intel/Apple Silicon variants, but cask eligibility is not Microsoft's current OS-support guarantee. Microsoft's Learn installation guide lists .NET10 on macOS14/15/26; the more recently dated .NET10 supported-OS matrix lists 15/26/27. These official pages differ. Use a current supported stable macOS and consult the linked matrix before deployment rather than relying on the cask's older minimum. macOS15 and26 appear in both retrieved references. Platform support also follows the OS publisher's lifecycle.

No extra formula dependency is declared in this cask. Ordinary SDK use does not require an IDE. Optional mobile/desktop workloads, Native AOT, native dependencies or device builds can require additional platform tools such as Xcode, workload packs or signing credentials. Package restore requires access to configured NuGet feeds. Microsoft does not give one universal RAM or storage minimum for all SDK workloads here; projects, caches, optional workloads and target platforms determine resource needs. On Apple Silicon, Arm64 .NET installs in the standard /usr/local/share/dotnet location; x64 installations use the documented x64 subdirectory, and PATH/DOTNET_ROOT selection can affect which architecture runs.

Conflicts and removal

Homebrew declares conflicts with dotnet-runtime, dotnet-runtime@preview and dotnet-sdk@preview. The SDK already includes matching runtimes, so do not install a conflicting runtime cask unnecessarily. SDKs and runtimes for other versions may coexist when installed through supported methods, but applications still need compatible runtimes and projects can pin SDKs. Avoid mixing architectures or installation methods without inspecting actual paths. PKG installation can require administrator authorization. Optional Homebrew zap cleanup is broad: it removes ~/.dotnet, ~/.nuget, path registrations and Microsoft .NET package receipts, potentially affecting other SDK versions, global tools and package caches. Back up and review installed versions before such cleanup.

Other platforms

Microsoft distributes SDK builds for Windows and supported Linux distributions as well as macOS. Architecture and native-library requirements differ by distribution. Optional .NET workloads can target Android, iOS, tvOS or Mac Catalyst; this does not mean this Mac cask installs an SDK directly on a phone. WPF and Windows Forms remain Windows-specific and do not become Mac applications just because the SDK is cross-platform. Consult the official .NET10 OS matrix and workload documentation for the intended target.

Accounts, cost and license

Local SDK development requires no Microsoft account or SDK subscription. .NET is free and open source; the SDK repository uses the MIT license with additional component notices. NuGet packages, commercial IDEs, private feeds, cloud hosting and signing services can have separate licenses, credentials or costs. SDK CLI telemetry sends usage data to Microsoft; the documented DOTNET_CLI_TELEMETRY_OPTOUT setting allows opting out. Editor extensions and their licensing are separate from the SDK.

Official references

• Mac installation
• Current .NET10 OS matrix
• Downloads
• SDK source
• CLI telemetry