[PR #976] Partially revert "Drop .NET 6.0, default to .NET 10.0 and update dependencies" #1392

New Issue

claunia · 2026-01-29T17:00:19Z

claunia commented

2026-01-29 17:00:19 +00:00

Original Pull Request: https://github.com/ElectronNET/Electron.NET/pull/976

State: closed
Merged: Yes

The key points are:

We have absolutely no need to drop .net6 support. It doesn't hurt us in any way
Many are still using .net6, including Electron.NET (non-Core) users. It doesn't make sense to force them to update two things at the same time (.net + Electron.NET
We MUST NOT and NEVER update Microsoft.Build.Utilities.Core. This will make Electron.NET stop working on older Visual Studio and MSBuild versions. There's are also no reasons to update it in the first place

I'd also like to note the MS saying "Out of support" has almost no practical meaning. I've never seen any bugs fixed in the same .net version which mattered to me. The bugs that all new .net versions have are much worse than mature .net versions which are declared as "out of support".

Also, MS have become more lazy in recent .net versions about downlevel support. From one day to another, out .net8 MAUI builds have stopped building on CI with a message that it's unsupported and we should update to .net 10 - only few weeks after .net 10 has been released - that's insane. It's not MS to decide at what time we will update our software - and definitely not within a timeframe of 4 weeks.

I know that many others are thinking the same way and therefore we should not drop support for older .net versions when we don't have a better reason than some MS support declaration.

**Original Pull Request:** https://github.com/ElectronNET/Electron.NET/pull/976 **State:** closed **Merged:** Yes --- The key points are: 1. We have absolutely no need to drop .net6 support. It doesn't hurt us in any way 2. Many are still using .net6, including Electron.NET (non-Core) users. It doesn't make sense to force them to update two things at the same time (.net + Electron.NET 3. We MUST NOT and NEVER update `Microsoft.Build.Utilities.Core`. This will make Electron.NET stop working on older Visual Studio and MSBuild versions. There's are also no reasons to update it in the first place I'd also like to note the MS saying "Out of support" has almost no practical meaning. I've never seen any bugs fixed in the same .net version which mattered to me. The bugs that all new .net versions have are much worse than mature .net versions which are declared as "out of support". Also, MS have become more lazy in recent .net versions about downlevel support. From one day to another, out .net8 MAUI builds have stopped building on CI with a message that it's unsupported and we should update to .net 10 - only few weeks after .net 10 has been released - that's insane. It's not MS to decide at what time we will update our software - and definitely not within a timeframe of 4 weeks. I know that many others are thinking the same way and therefore we should not drop support for older .net versions when we don't have a better reason than some MS support declaration.

claunia added the pull-request label 2026-01-29 17:00:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#1392