| ▲ | pjmlp 3 hours ago | ||||||||||||||||||||||
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. | |||||||||||||||||||||||
| ▲ | foepys 3 hours ago | parent | next [-] | ||||||||||||||||||||||
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. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | croes 2 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
.Net Framework 4.8 has a longer life cycle as the current .NET version | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | sippeangelo 2 hours ago | parent | prev [-] | ||||||||||||||||||||||
.NET Framework 5 or .NET Core 5? | |||||||||||||||||||||||
| |||||||||||||||||||||||