Try adding some .NET 10 support

[Numpsy]

refs #4296

Basically cloned from the changes to add .NET 9 support, as I'm learning this as I go along.

As it stands the new tests don't quite work because the tryNormalizeVersion function is parsing the 10 in net10-windows into 1.0 instead of 10.0 - I haven't had time to look at that further.

[Numpsy]

parsing the 10 in net10-windows into 1.0

Saying that, the MS Docs list net11 as being .NET Framework 1.1, so I suppose you can't try treating 10/11 as 10.0/11.0 in that case

[methvind]

There's now an official release candidate for .NET 10 and a supporting preview version of Visual Studio 2026. Chances are high that people will start experimenting with .NET 10 because of these releases.

Thanks to Numpsy for your work on this! Has there been other conversation about accepting these changes to support .NET 10? Is there other work that needs to be done to get a new version of Paket out? Are there ways I or other contributors could help get this moving again?

[Numpsy]

I haven't seen any other discussion besides the linked issues.

There don't appear to be any CI builds of recent PRs so possibly it hasn't had an official test run yet either

[gdziadkiewicz]

Hi @Numpsy , I got the App Veyor running for my fork. The build for current master is running here https://ci.appveyor.com/project/gdziadkiewicz/paket/builds/52894977 and the build for your net10 branch is running here https://ci.appveyor.com/project/gdziadkiewicz/paket/builds/52895002

My 2 cents on the net10 thing - during my update to net10.0 in a nuget-only solution net10 was interpreted as net1.0 by msbuild and I had to go with net10.0 to make it work in the end (you cane see that here https://gitlab.com/gdziadkiewicz/log4net.Ext.Json/-/jobs/11622968893#L39 ). Maybe Paket could do the same (force calling it net10.0)?