.NET Framework
By Microsoft
NET Framework is Microsoft's original managed application runtime and class library set for building and running Windows software. NET for web applications, and Windows Forms and WPF for desktop UIs, all installed as a component of Windows…
Definition
.NET Framework is Microsoft's original managed application runtime and class library set for building and running Windows software. Introduced in the early 2000s, it bundles the Common Language Runtime with a large base class library, ASP.NET for web applications, and Windows Forms and WPF for desktop UIs, all installed as a component of Windows rather than distributed with each application. It remains in long-term maintenance for existing Windows applications but is not the platform used for new cross-platform development.
Overview
.NET Framework was Microsoft's answer to Java in the early 2000s: a managed, garbage-collected runtime with a unified class library intended to replace the fragmented mix of Win32 API calls, COM components, and Visual Basic 6 runtime dependencies that Windows developers had relied on. It shipped as an operating system component that applications targeted rather than bundled, meaning a machine needed the correct version installed before an application built against it would run, and multiple versions could coexist side by side on the same machine. Mechanically, it works like other CLR-based platforms: source in C#, VB.NET, or F# compiles to Common Intermediate Language, which the installed CLR just-in-time compiles to native code at run time, backed by a generational garbage collector and a strongly typed metadata system. What distinguishes it from later .NET is its deep integration with Windows-specific technologies: COM interop for talking to legacy ActiveX and Office automation components, full Windows Forms and WPF desktop UI stacks, and Windows Communication Foundation for SOAP-based service communication, none of which needed to be portable because the platform never targeted other operating systems. Its direct successor and the platform now recommended for new work is .NET (formerly .NET Core), which reimplemented equivalent APIs on a cross-platform, open-source runtime while deliberately dropping or reworking Windows-only technologies like WCF server hosting and some COM interop scenarios. .NET Framework itself is frozen at version 4.8.x, receiving only security and reliability fixes as part of Windows servicing, not new features, which distinguishes it from the actively evolved .NET release train. In practice, .NET Framework remains in wide use inside large enterprises running legacy line-of-business applications: WCF services, ASP.NET Web Forms sites, and desktop tools built over the past two decades that would require substantial rework to port. Organizations often keep such applications on .NET Framework indefinitely, isolating them behind current Windows Server versions, while directing all new development to .NET. The limitations are largely about what it lacks going forward: no official cross-platform support, no involvement in the modern performance and trimming improvements shipped in newer .NET releases, and a fixed feature set that will not gain support for newer language versions beyond what C# and VB already support on the shared compiler. Teams maintaining .NET Framework code should plan for eventual migration, since Microsoft's investment and most third-party library updates now target .NET rather than the Framework. Tooling vendors have largely followed the same path, with newer versions of testing frameworks, static analysis tools, and IDE features increasingly assuming a .NET target rather than treating .NET Framework as a first-class citizen going forward.
Key Features
- Common Language Runtime with just-in-time compilation and garbage collection
- Deep COM interop for legacy ActiveX and Office automation components
- Windows Forms and WPF for native Windows desktop applications
- Windows Communication Foundation for SOAP and WS-* service hosting
- ASP.NET Web Forms and MVC for server-rendered web applications
- Installed as a shared Windows component rather than bundled per app
- Side-by-side versioning allowing multiple Framework versions on one machine
- Long-term maintenance mode limited to security and reliability patches