The open-source runtime and libraries for .NET, enabling cross-platform development for cloud, mobile, desktop, and IoT applications.
.NET Runtime is the core execution engine and library foundation for the .NET platform, enabling developers to build and run applications across cloud, mobile, desktop, and IoT environments. It provides the essential components like the runtime, class libraries, and the `dotnet` host installer that manage application execution. The project solves the problem of creating high-performance, cross-platform applications with a consistent set of tools and APIs.
Developers building applications in C#, F#, or Visual Basic that need to run on multiple platforms (Windows, Linux, macOS, IoT). It's also for contributors interested in low-level runtime development, library design, or improving the .NET ecosystem.
Developers choose .NET Runtime for its open-source nature, strong cross-platform support, and comprehensive standard libraries that reduce boilerplate code. Its integration with the broader .NET toolchain and active community provide a reliable foundation for both new projects and migrating legacy applications.
.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports Windows, Linux, macOS, and IoT devices, enabling consistent application deployment across diverse environments as highlighted in the key features.
Community-driven development with public issue tracking, contribution guidelines, and active Discord discussions, fostering a transparent ecosystem.
Features a dedicated security reporting process via the Microsoft Security Response Center with a 24-hour response time, ensuring vulnerabilities are handled promptly.
Includes the shared host (`dotnet`) installer and CLI tools for managing applications and SDKs, simplifying deployment and development workflows.
Building and testing the runtime requires following detailed workflow instructions, which can be a barrier for new contributors despite 'good first issue' labels.
Heavily backed by Microsoft, which may lead to prioritization of Windows-centric features or integration with Azure services over community-driven alternatives.
The full runtime and libraries can be bulky for lightweight applications, compared to more minimal runtimes available in other ecosystems.