Urgent.News

What's breaking now, across thousands of outlets.

Tech

.NET Framework vs .NET Core vs .NET 5+ — the history explained — .NET Internals

Lesson 1 of 11 in the free .NET Internals — CLR, CTS, CLS, IL, JIT, Memory Management & Garbage Collection course on DevLadder. .NET Framework .NET Core 1–3.1 .NET 5+ Years 2002–2019 (4.8.1 in 2022) 2016–2019 2020 → OS Windows only Windows, Linux, macOS Windows, Linux, macOS, mobile (MAUI), WebAssembly Source Closed (reference source available) Open source (MIT) Open source Deployment…

The .NET Framework, .NET Core, and .NET 5+ represent three distinct versions of the popular .NET software development platform. The history of these versions spans from 2002 to 2022, with .NET 5+ being released in 2020. The .NET Framework was initially released for the Windows operating system only, while .NET Core brought multi-platform support, including Windows, Linux, and macOS. As of 2022, .NET 5+ supports Windows, Linux, macOS, mobile (MAUI), WebAssembly, and single-file executables.

The .NET Framework has been maintained for machine-wide installation, as part of Windows, and also as a side-by-side deployment. On the other hand, .NET Core offers same deployment mode along with self-contained deployments and Native AOT (Ahead-of-Time) compilation for reduced startup time. .NET 5+ takes it a step further by offering single-file executables, Native AOT, and improved performance.

ASP.NET, a web application framework, evolved alongside these versions. ASP.NET Web Forms, MVC 5, and ASP.NET Web API 2 were used with .NET Framework, while ASP.NET Core, ASP.NET Core MVC, and ASP.NET Core Web API are the corresponding frameworks for .NET Core and .NET 5+. Performance-wise, .NET Framework offers good performance; .NET Core is much faster, and .NET 5+ is the fastest, with performance improvements in each release.

The Common Language Runtime (CLR) serves as the execution engine for .NET, handling tasks such as loading assemblies, verifying type safety, JIT-compiling Intermediate Language (IL) code to native machine code, memory management using the garbage collector, exception handling, thread and synchronization management, and providing interop with native code and debugging/profiling services. Code executed under the CLR is considered "managed code."

Two key concepts in .NET are the Common Type System (CTS) and the Common Language Specification (CLS). CTS defines how types are declared and used across .NET languages like C# and VB.NET, ensuring a shared type system. CLS is a subset of CTS rules that every .NET language supports, allowing CLS-compliant libraries to be used across different languages without compatibility issues.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

What a Successful Code Scan Does Not Prove

Quick answer: A successful scan proves the document was rebuilt from routes the scan could resolve, and nothing more. It does not prove the implementation conforms to the spec, behaves correctly at…

Program structure, modules and the Main method — VB.NET

Lesson 1 of 12 in the free VB.NET — Visual Basic .NET from Basics to Advanced (with C# Comparison) course on DevLadder. Option Strict On ' no implicit narrowing conversions or late binding — always…

  • VB.NET structures cover Program modules and Main method importance
  • Option Strict On avoids implicit narrowing conversions
  • Sub Main with String() parameters is program entry point

Class, object, fields, properties and methods — OOP Concepts in C#

Lesson 1 of 15 in the free OOP Concepts in C# course on DevLadder. A class is a blueprint; an object is an instance created from it at runtime.

  • A class is a blueprint for objects in C#, likened to a template.
  • Objects are instances of classes generated at runtime with their own state.
  • Encapsulation safeguards class data by making fields private and providing public access methods.

S — Single Responsibility Principle — SOLID Principles with Examples

Lesson 1 of 8 in the free SOLID Principles with Examples course on DevLadder. "A class should have one, and only one, reason to change." — Robert C.

  • Single Responsibility Principle (SRP) states a class should have one reason to change
  • Changing invoice formatting, data storage, or email delivery requires class modifications

More from Sunday 8 November →