News for hackers. Stuff that matters.
Re:I Fixed Windows Native Development by pjmlp on Sunday February 15, 2026 @09:33AM (#47023996)
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.

Re:I Fixed Windows Native Development by foepys on Sunday February 15, 2026 @10:00AM (#47024230)
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.

Re:I Fixed Windows Native Development by pjmlp on Sunday February 15, 2026 @10:32AM (#47024465)
Most likely never will, because WinRT is the future and WinRT has replaced type libraries with .NET metadata. At least from MS point of view.

The current solution is to use the CLI tools just like C++.

However have you looked into ComWrappers introduced in .NET 8, with later improvements?

I still see VB 6 and Delphi as the best development experience for COM, in .NET it wasn't never that great, there are full books about doing COM in .NET.

Re:I Fixed Windows Native Development by croes on Sunday February 15, 2026 @10:14AM (#47024343)
.Net Framework 4.8 has a longer life cycle as the current .NET version
Re:I Fixed Windows Native Development by 8cvor6j844qw_d6 on Sunday February 15, 2026 @10:56AM (#47024708)
When I first worked with dot NET I was confused with the naming and version numbers.
Re:I Fixed Windows Native Development by ozim on Sunday February 15, 2026 @11:08AM (#47024808)
This argument against .NET annoys me.

Because that’s pretty much any freaking thing - oh Python, oh PHP, oh driving a fork lift, oh driving a car.

Once you invest time in using and learning it is non issue.

I do get pissed off when I want to use some Python lib bit it just doesn’t work out of the box, but there is nothing that works out the box without investing some time.

Just like a car get a teenager into a car he will drive into first tree.

Posting BS on Facebook shouldn’t be benchmark for how easy things should be.

Re:I Fixed Windows Native Development by pjmlp on Sunday February 15, 2026 @10:33AM (#47024468)
It does, but current versions can be shipped with the application.

Thus this should be less of a problem.

Re:I Fixed Windows Native Development by sippeangelo on Sunday February 15, 2026 @11:01AM (#47024756)
.NET Framework 5 or .NET Core 5?
Re:I Fixed Windows Native Development by afdbcreid on Sunday February 15, 2026 @11:50AM (#47025182)
There is no .NET Framework 5. .NET Core 5 is just .NET 5.