NuGet package naming

[akamyshanov]

First of all, congratulations and thank you for finally publishing the project on NuGet 🎉

I fully understand that this is very subjective, however here are my 2 cents.
I think that the package IDs should have a different naming structure. Typically, dots in .NET world represent namespace or subproject separators. This means that QuickFIXn.FIX4.1 is logically divided into:

• QuickFIXn (Project name, OK)
• FIX4 (???)
• 1 (???)

This is even worse with QuickFIXn.FIX5.0SP2:

• QuickFIXn
• FIX5
• 0SP2

I think that the project and assembly naming structure is much more clear, e.g:

• QuickFIXn.FIX44 instead of QuickFIXn.FIX4.4
• QuickFIXn.FIX50SP2 instead of QuickFIXn.FIX5.0SP1

So that FIX44 or FIX50SP2 represent the spec version as a single entity.

I understand that this would break backwards compatibility for those who already downloaded the packages but I strongly believe that it would be better to change the naming in the long run.

[amandengue]

👍
I totally agree with this

[gbirchmeier]

I agree with this too. We'll probably announce this upcoming change in the 1.13 release and put it in the READMEs, but not actually execute the change until 1.14.