+1 for me.I think as long as we keep a 1.7.x branch for anyone who may need
changes for the older versions. 4.5 is now 5 years old. Its like artemis
supports java 8+ now. If issue for older wed have to goto old version.Having a
clean slate with .net std for 1.8 sounds sensible.Also really great to have you
contribute and helping update our nms Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: "Heiser, Derek" <[email protected]>
Date: 17/04/2019 16:10 (GMT+00:00) To: [email protected] Subject:
AMQNET-565: .net standard port Hello all,I wanted to try my hand at this
feature request:
https://issues.apache.org/jira/projects/AMQNET/issues/AMQNET-565?filter=allopenissues
to port ActiveMQ to .Net Standard. I’ve started working on a fork here:
https://github.com/killnine/activemq-nms-api/tree/refactor but wanted some
feedback from contributors before I sink too much time in.The current build
(1.7.2) supports .net 2.0, 3.5, and 4.0.Net standard 2.0, by default, supports
back to 4.6.1. I’ve looked into supporting multiple target frameworks (for
instance, .net standard 1.2 supports 4.5.1) but there are some pretty gnarly
conflicts (ex: System.Transactions, NUnit 3, serialization attributes) between
even .net standard 1.2 and the latest .net standard.My recommendation would be
to treat 1.7.2 as the legacy package and make this change a 1.8.0 build as a
fresh start to support 4.6.1 and above with netstandard 2.0. I thing we could
update the README to explain the support for earlier frameworks. I totally
understand the need to support older platforms, but I think keeping 1.7.2
around and moving forward ensures we aren’t hamstrung by the very clear
direction from Microsoft that Netstandard is the way forward.There’s other
issues I’d like to address with the solution organization but figured this was
the biggest point of discussion right now…I’m on the Slack channel if you want
to discuss off the record 😉Thanks!Derek HeiserFollow Us:
Facebook<http://www.qg.com/social1> | Twitter<http://www.qg.com/social2> |
LinkedIn<http://www.qg.com/social3> | YouTube<http://www.qg.com/social4>
