fluffynuts commented on issue #111:
URL:
https://github.com/apache/logging-log4net/issues/111#issuecomment-1961293978
btw targeting netstandard & .net 4.6.2 is trivial with the Mono shim - it's
how I do all my personal packages where I expect them to be used on netfx, eg
NExpect,
fluffynuts commented on issue #111:
URL:
https://github.com/apache/logging-log4net/issues/111#issuecomment-1961289081
I would still want to maintain a net462 package (and whatever comes after
that in NETFX-world's support matrix - right now, that's the lowest version of
.net framework
FreeAndNil commented on issue #111:
URL:
https://github.com/apache/logging-log4net/issues/111#issuecomment-1961174876
I don't think so.
When we support netstandard2.0, you can use the package from every supported
target framework.
Do you have a use case in mind where this would
gitkrasty commented on issue #111:
URL:
https://github.com/apache/logging-log4net/issues/111#issuecomment-1961114741
Is multitargeting at least to the latest supported .NET runtimes still an
option?
--
This is an automated message from the Apache Git Service.
To respond to the message,
fluffynuts commented on issue #111:
URL:
https://github.com/apache/logging-log4net/issues/111#issuecomment-1938610998
I think if we do this, it's probably a good idea to do a major version bump,
so that no-one requiring an older version would accidentally install a newer
one with what
FreeAndNil commented on issue #111:
URL:
https://github.com/apache/logging-log4net/issues/111#issuecomment-1936525782
+1 from me.
I think supporting net462 & netstandard2.0 is enough for everyone who is
able and willing to upgrade their depencies to newer versions.
--
This is an
