4 ms·

Not really the same, .NET Framework is a dead end, current .NET (former Core) is quite different, you can't port .NET Framework 4.8 apps to .NET 8

• neonsunset 2y ago
  You can. C# 1.0 is still valid syntax, and library authors can target both legacy and current day versions of .NET with netstandard2.0 target. Most libraries do just that. Moreover, there are still some applications that get to use modern runtime-independent language features and SDK-style projects (terse Cargo.toml-like project manifests, still XML but they are very readable) while targeting both .NET Framework 4.8 and .NET 8 at the same time (and everything in-between them). Hell, I've seen projects[0] which look relatively modern but for some reason still target .NET Framework 3.5, I do not condone that, but it is doable and sometimes there are reasons for it. [0]: https://github.com/Kevin-Robertson/Inveigh/blob/master/Inveigh/Protocols/Quiddity/Quiddity/Quiddity.csproj#L4 https://github.com/Kevin-Robertson/Inveigh/blob/master/Invei...
  • albertopv 2y ago
    You can do (almost) everything with enough time and resources, but it can be tough. WCF, without CoreWCF couldn't migrate until 2022 release and .Net Core 1.0 was released in 2019. EF Core is different. WPF, ASP .Net WebForms... Microsoft Message Queues usage is a no go. So yes, you can, not always, not easy, often not worth.
    • neonsunset 2y ago
      (2016) https://devblogs.microsoft.com/dotnet/announcing-net-core-1-0/ https://devblogs.microsoft.com/dotnet/announcing-net-core-1-...