The BCL and CoreLib

The Base Class Library (BCL)

The BCL is a comprehensive set of fundamental libraries that provide a wide range of common functionality. These include types for collections, file I/O, string manipulation, networking, cryptography, reflection, and more. BCL namespaces typically start with System.* and, to a lesser extent, Microsoft.*. It forms the lower layer on which higher-level application frameworks like ASP.NET Core are built. File and network I/O in it are built on streamsStreamsReading and writing data as a flow of bytes, a chunk at a time.Opens in a new tab.

System.Private.CoreLib.dll

In .NET (Core) and later, System.Private.CoreLib.dll, often called CoreLib, is the most fundamental assembly. It defines the core types necessary for the CLR’s Virtual Object System, such as System.Object, System.String, System.Int32 and other primitive types. It is very tightly coupled with CoreCLR, because the CLR must load CoreLib on startup to function.

How CoreLib and CoreCLR work together

CoreLib contains managed code that often needs to call into native CLR functions for low-level operations, for example triggering garbage collection, loading types, or interacting with the operating system. Conversely, the CLR also needs to call into managed code in CoreLib. This close interaction is essential for the runtime’s operation.

The modular nature of .NET (Core) means applications often only need to deploy the parts of the BCL they actually use. That gives smaller deployment sizes than the monolithic .NET Framework.

The architecture of .NET (Core), with its cross-platform CoreCLR and modular BCL, facilitates modern development practices. It lets you build applications that run in diverse environments, such as Linux containers, and it enables smaller, more optimized deployments, since applications typically only bundle the BCL components they need.