logoalt Hacker News

pjmlptoday at 2:33 PM3 repliesview on HN

Which has been fixed on .NET 5 and later.

.NET Framework should only be used for legacy applications.

Unfortunately there are still many around that depend on .NET Framework.


Replies

foepystoday at 3:00 PM

Since .NET 10 still doesn't support Type Libraries quite a few new Windows projects must be written in .NET Framework.

Microsoft sadly doesn't prioritize this so this might still be the case for a couple of years.

One thing I credit MS for is that they make it very easy to use modern C# features in .NET Framework. You can easily write new Framework assemblies with a lot of C# 14 features. You can also add a few interfaces and get most of it working (although not optimized by the CLR, e.g. Span). For an example see this project: https://www.nuget.org/packages/PolySharp/

It's also easy to target multiple framework with the same code, so you can write libraries that work in .NET programs and .NET Framework programs.

show 1 reply
sippeangelotoday at 4:01 PM

.NET Framework 5 or .NET Core 5?

show 1 reply
croestoday at 3:14 PM

.Net Framework 4.8 has a longer life cycle as the current .NET version

show 2 replies