Understanding .NET Framework Compatibility
2 Technology Post dotnet, softwaredevelopment, coding Jan 1, 2025 1735776000000
For those trying to understand .NET framework compatibility, It’s taken me several days to map it out. I am working on static analysis of .NET legacy systems and have working code to build Abstract Symbol Trees by dynamically loading assemblies if compatible, assembly metadata if not. If you have corrections, let me know, PLEASE.
First, there are three types of .NET targets. .NET Framework, .NET Core, .NET Standard. Framework and Core are runtimes, Standard is a specification.
- .NET Framework: Original Windows-only platform. Coupled to Windows APIs. 2002-2016.
- .NET Core: Cross-platform, open-source. Higher performance, modular design. 2016+
- .NET Standard: Specification defining common APIs that both Framework and Core must implement. Enables code sharing between platforms but isn’t a runtime itself - just an interface contract. 2016+
.NET Standard 2.0+:
- Can target .NET Framework 4.61+
- Works with all .NET Core versions
- Targets same or higher .NET Standard versions
.NET Standard 1.x:
- Only targets higher .NET Standard versions
- No compatibility with Framework/Core .NET Framework:
.NET Framework:
- Can’t target .NET Core
- Can’t target .NET Standard
- Only works with same/higher Framework versions
.NET Core:
- Compatible with .NET Standard 2.0
- No .NET Framework compatibility
- Works with same/higher Core versions
#dotnet #softwaredevelopment #testing #coding
