All 19 CLR & Runtime questions
More in CLR & Runtime
What is the difference between managed and unmanaged code in .NET, and when would you need to work with the latter? What is JIT (Just-In-Time) compilation, and how does it differ from ahead-of-time (AOT) compilation? How does the CLR's type system distinguish between value types and reference types, and where is each typically allocated? What is the Common Type System (CTS), and how does it enable interoperability between different .NET languages? What does the `unsafe` keyword and pointer usage in C# allow, and why would a developer opt into it? What is the difference between the CLR's Server GC and Workstation GC modes, and how do you choose between them? What is the AppDomain concept in .NET Framework, and why was it removed from modern .NET? What is tiered compilation, and how does it balance fast startup with peak execution performance? What is boxing and unboxing, and what performance cost does it incur? How does the CLR handle exceptions at a low level, and what is the performance implication of throwing exceptions frequently?
Advertisement
Back to results for “Performance”
.NET › CLR & Runtime

What is the relationship between the CLR and the .NET class library (BCL - Base Class Library)?

Intermediate

Answer

The CLR is the execution engine (memory management, JIT, type system), while the Base Class Library is the vast collection of pre-built types and APIs (collections, I/O, networking, LINQ, string manipulation) that applications actually call -- the BCL itself is written in C# (and some C++ for performance-critical low-level pieces) and runs on top of the CLR just like any application code, providing the foundational building blocks every .NET program relies on.
// BCL types used constantly, running on top of the CLR
List<string> names = new();
StreamReader reader = new StreamReader("file.txt");
var result = names.Where(n => n.StartsWith("A")).ToList();  // LINQ, part of BCL
Real-world example Understanding this layering clarifies why upgrading the CLR/runtime version (e.g., .NET 6 to .NET 8) can bring both execution engine improvements (faster JIT) and BCL improvements (new APIs, optimized implementations of existing ones) simultaneously.

Common follow-ups: What parts of the BCL are implemented in C# versus lower-level languages?;How do you distinguish a CLR-level feature from a BCL-level API in documentation?

CLR & Runtime;Diagnostics & Performance
All 19 CLR & Runtime questions