[
https://issues.apache.org/jira/browse/TINKERPOP-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549168#comment-16549168
]
Florian Hockmann commented on TINKERPOP-2012:
---------------------------------------------
I guess it would make sense to upgrade to .NET Standard 2.0 for TinkerPop 3.4.0
as it is really a breaking change and maybe add .NET Standard 2.0 as an
additional target for the tp33 and tp32 branches if it doesn't require too much
effort or otherwise leave those branches unchanged. Any other opinions?
> Target .NET Standard 2.0 for Gremlin.Net
> ----------------------------------------
>
> Key: TINKERPOP-2012
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2012
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.3.3, 3.2.9
> Reporter: Florian Hockmann
> Priority: Major
>
> The general recommendation from the .NET team is now to target .NET Standard
> 2.0 instead of the lowest version possible (which was the recommendation
> until .NET Standard 2.0):
> {quote}I know we said target The lowest netstandard but we really want
> everyone to re-baseline at netstandard 2.0. At the very least add a
> netstandard 2.0 target.
> {quote}
> [Source|https://twitter.com/davidfowl/status/1008453902058917888]
> Apart from an increased API surface compared to .NET Standard 1.x, .NET
> Standard reduces the dependency graph of libraries. Right now the
> dependencies for Gremlin.Net look like this:
> *.NETStandard 1.3*
> * NETStandard.Library (>= 1.6.1)
> * Newtonsoft.Json (>= 9.0.1)
> * System.Net.WebSockets (>= 4.3.0)
> * System.Net.WebSockets.Client (>= 4.3.0)
> * System.Reflection.TypeExtensions (>= 4.3.0)
> With .NET Standard 2.0, the only dependency left should be Newtonsoft.Json.
> We have to decide whether we want to upgrade from .NET Standard 1.3 or to
> just add .NET Standard 2.0 as an additional target framework. Upgrading would
> mean that consuming applications would need slightly newer framework versions
> (e.g. .NET Framework 4.6.1 instead of 4.6 or Mono 5.4 instead of 4.6).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
