{{Quickfixn}} Quickfixn Digest, Vol 125, Issue 1

[Francis Gingras]

I think . NET6 is the way forward, but assuming that projects can be
upgraded to .NET6 is incorrect. For example: we use a library that had a
EOL 10 years ago and no source code. We don't have the time or budget to
get rid of it. It's just not worth the risk of new bugs. It still runs fine
on 4.8 but i have no idea if it will run on 6 so we have to stick to 4.8.

But go ahead with .net6. You have to keep up with the game..

Francis



On Fri, Dec 16, 2022 at 4:23 AM <quickfixn-request at lists.quickfixn.com>
wrote:

> Send Quickfixn mailing list submissions to
>         quickfixn at lists.quickfixn.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
> or, via email, send a message with subject or body 'help' to
>         quickfixn-request at lists.quickfixn.com
>
> You can reach the person managing the list at
>         quickfixn-owner at lists.quickfixn.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Quickfixn digest..."
> Today's Topics:
>
>    1.  moving the next QF/n release to net6.0? (Grant Birchmeier)
>    2.  getting rid of deprecations in next release (Grant Birchmeier)
>    3. Re:  getting rid of deprecations in next release (Artur Pietrzyk)
>
>
>
> ---------- Forwarded message ----------
> From: Grant Birchmeier <gbirchmeier at connamara.com>
> To: "Mailing list for QuickFIX/n" <quickfixn at lists.quickfixn.com>
> Cc:
> Bcc:
> Date: Thu, 15 Dec 2022 17:48:03 -0600
> Subject: {{Quickfixn}} moving the next QF/n release to net6.0?
> Hi all,
>
> After a far-too-long period of inactivity, I have some time to put into
> QF/n again.  We are overdue for a new release, and I'm working on it, but I
> have an important question:
>
> *Is there a potential downside to moving QF/n to the "net6.0" framework
> target?*  (Currently it's on "netstandard2.0")
>
> We have one enhancement in mind that needs a more recent .NET feature, and
> I'm sure there will be more.  .NET 5 has been EOL'd, so .NET 6 seems to be
> the way to go.  We figure many financial firms need to be on non-EOL
> libraries anyway, so I'm not sure if this would affect many users.
>
> (And yes, I am aware of Issue #713, which will be addressed.)
>
> -Grant
>
> --
> Grant Birchmeier
> Connamara Systems, LLC
> http://connamara.com
>
> This email, along with any attachments, is confidential. If you believe
> you received this message in error, please contact the sender immediately
> and delete all copies of the message. Thank you from Connamara Systems, LLC.
>
>
> ---------- Forwarded message ----------
> From: Grant Birchmeier <gbirchmeier at connamara.com>
> To: "Mailing list for QuickFIX/n" <quickfixn at lists.quickfixn.com>
> Cc:
> Bcc:
> Date: Thu, 15 Dec 2022 17:56:58 -0600
> Subject: {{Quickfixn}} getting rid of deprecations in next release
> Hi all again,
>
> I plan on getting rid of deprecated code in the next release.
>
> I don't think this will affect many people, because most of the
> deprecations are deep in engine code that most clients don't touch.
>
> However, if you see deprecation warnings when you are building your app, I
> highly encourage you to get rid of those.  Most deprecation warnings should
> tell you what the right thing to call is, so I think it would be an easy
> task.  If you have any questions about any deprecation warnings, please ask
> (because I probably wrote those warnings!).
>
> Note: I will not be bumping the major release number, e.g. this will not
> be "QuickFIX/n 2.0".  I know that, technically, semantic versioning would
> require me to do that, but (1) I don't think this will actually affect
> anyone, and (2) this isn't going to "feel" like a major release and I don't
> want the new number to give anyone a false idea.
>
> -Grant
>
> --
> Grant Birchmeier
> Connamara Systems, LLC
> http://connamara.com
>
> This email, along with any attachments, is confidential. If you believe
> you received this message in error, please contact the sender immediately
> and delete all copies of the message. Thank you from Connamara Systems, LLC.
>
>
> ---------- Forwarded message ----------
> From: Artur Pietrzyk <apietrzyk at coinapi.io>
> To: "Mailing list for QuickFIX/n" <quickfixn at lists.quickfixn.com>
> Cc:
> Bcc:
> Date: Fri, 16 Dec 2022 09:23:25 +0000
> Subject: Re: {{Quickfixn}} getting rid of deprecations in next release
> Hi Grant,
>
> This removing of legacy code will include it be working on newest
> supported net version? There is bug preventing it working above net5.0.
>
> Artur Pietrzyk
> CEO and Founder
> www.coinapi.io
>
>
> On Fri, Dec 16, 2022 at 12:56 AM, Grant Birchmeier <
> gbirchmeier at connamara.com> wrote:
>
>> Hi all again,
>>
>> I plan on getting rid of deprecated code in the next release.
>>
>> I don't think this will affect many people, because most of the
>> deprecations are deep in engine code that most clients don't touch.
>>
>> However, if you see deprecation warnings when you are building your app,
>> I highly encourage you to get rid of those.  Most deprecation warnings
>> should tell you what the right thing to call is, so I think it would be an
>> easy task.  If you have any questions about any deprecation warnings,
>> please ask (because I probably wrote those warnings!).
>>
>> Note: I will not be bumping the major release number, e.g. this will not
>> be "QuickFIX/n 2.0".  I know that, technically, semantic versioning would
>> require me to do that, but (1) I don't think this will actually affect
>> anyone, and (2) this isn't going to "feel" like a major release and I don't
>> want the new number to give anyone a false idea.
>>
>> -Grant
>>
>> --
>> Grant Birchmeier
>> Connamara Systems, LLC
>> http://connamara.com
>>
>> This email, along with any attachments, is confidential. If you believe
>> you received this message in error, please contact the sender immediately
>> and delete all copies of the message. Thank you from Connamara Systems, LLC.
>>
>> _______________________________________________
>> Quickfixn mailing list
>> Quickfixn at lists.quickfixn.com
>> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>>
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20221216/3d2d3c5f/attachment-0001.htm>