Add .net9 and .net10 in nuget Package

[ignazgebinde]

Hi quickfixn team!

Please consider adding all current .net core frameworks in the nuget package. Instead of net8.0 use net8.0;net9.0;net10.0

I know basically it is possible to use a net8 version i higher versions, but when build in a higher version some featurs like "Pattern matching enhancements" or "Compiler optimizations" in the (Intermediate Language) could lead to a better runtime.

Furthermore, all users of the NuGet package can see that it targets the latest framework, which increases the credibility and perceived quality of the product.

Thank you for your time

BR ignazgebinde

[Rob-Hague]

I know basically it is possible to use a net8 version i higher versions, but when build in a higher version some featurs like "Pattern matching enhancements" or "Compiler optimizations" in the (Intermediate Language) could lead to a better runtime.

So long as the library is built and packaged using the latest .NET SDK, such improvements are available to consuming runtimes. The target frameworks effectively just define the API surface that is available to be used in the library.

[ignazgebinde]

I know basically it is possible to use a net8 version i higher versions, but when build in a higher version some featurs like "Pattern matching enhancements" or "Compiler optimizations" in the (Intermediate Language) could lead to a better runtime.

So long as the library is built and packaged using the latest .NET SDK, such improvements are available to consuming runtimes. The target frameworks effectively just define the API surface that is available to be used in the library.

Thank you for you explanation, but it does not confirms my observations.
I used the 6edfc2a master branch and added net8.0;net10.0

Than i took the dll and run the IL Disassembler from the developer console
ildasm.exe .\net10.0\QuickFix.dll /out=10.il
ildasm.exe .\net8.0\QuickFix.dll /out=8.il

This generates the intermediate language code of both artefacts. I compared them and found new features like
IL_007f: call valuetype [System.Runtime]System.ReadOnlySpan1<!0>`

IL_0175: call bool [System.Memory]System.MemoryExtensions::Contains<int32>

Therefore, I kindly ask that the additional runtimes be included in the *.csproj files as well.

BR ignazgebinde

[Rob-Hague]

Ok interesting, TIL. Although from what I saw, the example you pointed out:

      IL_00cf:  ldarg.2
+     IL_00d0:  call       valuetype [System.Runtime]System.ReadOnlySpan`1<!0> valuetype [System.Runtime]System.ReadOnlySpan`1<int32>::op_Implicit(!0[])
      IL_00d5:  ldloc.s    V_7
      IL_00d7:  callvirt   instance int32 QuickFix.Fields.IField::get_Tag()
-     IL_00d7:  call       bool [System.Linq]System.Linq.Enumerable::Contains<int32>(class [System.Runtime]System.Collections.Generic.IEnumerable`1<!!0>,
+     IL_00dc:  call       bool [System.Memory]System.MemoryExtensions::Contains<int32>(valuetype [System.Runtime]System.ReadOnlySpan`1<!!0>,
                                                                                        !!0)
      IL_00e1:  brtrue.s   IL_010c

... appears twice, and none of the other differences seem that interesting

[ignazgebinde]

Would it be possible to add the other currently active .NET Core frameworks to the NuGet package?
The reasons outlined in the post above provide several arguments in favor of adding them.
If this is not possible, could you please close the issue and provide the reason why?

BR ignazgebinde

[gbirchmeier]

It's not a bad idea and I will look into it.

Just a quick reminder: This project is free, and I work on it when I have rare spots of free time between projects. Sometimes a client will directly or indirectly fund new features. As much as I would like to go full-time on all the issues and clear the backlog, I am just not able to.

That said, .NET 9 and 10 both reach end-of-support on November 10, 2026. I do think it would be smart to add .NET 10 to the package. I will probably skip 9 though.

[ignazgebinde]

Sounds like a good plan for me. Thank you for your effort, spending time between your other work to support this project. I never intended to push someone.
BR ignazgebinde

[JustinJmnz]

I's like to start contributing to this project - but this repository mentions specifically not to update the framework versions. Is this still true?

@gbirchmeier

[gbirchmeier]

@JustinJmnz I appreciate the enthusiasm. However, updating the framework is a pretty quick and easy task. When I have time to spin a new release, I will do it.