Frameworks

.NET Core vs .NET Framework

.NET Framework vs .NET Core explained: where each runs, why Core became plain .NET, how to spot net48 or net10.0, and when the Windows-only runtime still fits.

  • 7 min read
  • 5 questions
  • +35 XP
Transcript

.NET Core vs .NET Framework, explained by cats. Kitty wants to build an app. She wants to use C-sharp, so Kitty tries downloading .NET. But she sees… .NET Framework. and .NET Core. Kitty’s confused. Are these the same cat? Or different cats?

So Kitty learns. .NET Framework is the old cat. Lives only on Windows. Big and Slow. Full of old code. But still running software. Don’t touch it. It might break. Then there’s .NET Core. also known as .NET, The new cat.

open source. It's Fast and Runs anywhere. Windows. Linux. Cloud. So now there are two .NETs. One old. One new. Same name. Different cats. If Kitty picks the wrong one. The App doesn’t run. Kitty cries. So Kitty chooses carefully. To make sure her app compiles.