explaingit

dotnet/corefx

Analysis updated 2026-06-24

17,499Audience · developerComplexity · 5/5LicenseSetup · hard

TLDR

Archived repository that held the standard class library implementations for .NET Core. Active development moved to dotnet/runtime, which merged CoreFX and CoreCLR.

Mindmap

mindmap
  root((corefx))
    Status
      Archived
      Servicing only
      Moved to dotnet/runtime
    Contents
      System.Collections
      System.IO
      System.Xml
    Use Cases
      Read .NET Core 2.1 source
      Patch legacy 3.1 code
      Study BCL history
    Tech Stack
      C#
      .NET Core
      MSBuild
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Read source for .NET Core 2.1 or 3.1 standard library classes for historical reference

USE CASE 2

Submit a servicing fix for an out-of-support .NET Core 2.1 or 3.1 release

USE CASE 3

Trace how a System.IO or System.Collections type was implemented before the dotnet/runtime merge

What is it built with?

C#.NET CoreMSBuild

How does it compare?

dotnet/corefxrqlite/rqliteapache/brpc
Stars17,49917,49917,501
LanguageGoC++
Setup difficultyhardeasyhard
Complexity5/54/55/5
Audiencedeveloperops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Repo is archived servicing-only, for active work use github.com/dotnet/runtime instead.

MIT lets anyone use, modify, and ship the code in commercial products, as long as the copyright notice is preserved.

In plain English

CoreFX was the library layer of .NET Core, Microsoft's open-source, cross-platform version of the .NET framework. This repository contained the standard library implementations that developers use when building .NET Core applications, including foundational components like System.Collections (data structures), System.IO (file and stream handling), and System.Xml (XML parsing), among many others. .NET Core itself is a runtime environment: when you write a C# or F# program and run it.NET Core is what executes it. CoreFX was the companion repo containing the class libraries, the pre-built tools and utilities that make up the "standard library" every .NET developer can call on. The actual runtime engine lived in a separate companion repository called CoreCLR. This repository is now archived. According to the description, it is only used for servicing maintenance updates for older versions (.NET Core 2.1 and 3.1). All active development has moved to the unified github.com/dotnet/runtime repository, which merged CoreFX and CoreCLR together. If you are looking to work with or contribute to .NET, that is the current home. The code is licensed under the MIT license and was maintained by Microsoft and open-source contributors as part of the .NET Foundation.

Copy-paste prompts

Prompt 1
Point me to the current dotnet/runtime path that replaced this corefx folder structure
Prompt 2
Show me where the .NET Core 3.1 System.Text.Json implementation lives in this repo
Prompt 3
Help me build a single corefx library locally to test a patch against .NET Core 3.1
Prompt 4
Compare the corefx folder layout with the equivalent areas in dotnet/runtime today

Frequently asked questions

What is corefx?

Archived repository that held the standard class library implementations for .NET Core. Active development moved to dotnet/runtime, which merged CoreFX and CoreCLR.

What license does corefx use?

MIT lets anyone use, modify, and ship the code in commercial products, as long as the copyright notice is preserved.

How hard is corefx to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is corefx for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub dotnet on gitmyhub

Verify against the repo before relying on details.