[ 
https://issues.apache.org/jira/browse/TINKERPOP-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Florian Hockmann closed TINKERPOP-2012.
---------------------------------------
       Resolution: Fixed
         Assignee: Florian Hockmann
    Fix Version/s: 3.2.10
                   3.3.4
                   3.4.0

> 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
>            Assignee: Florian Hockmann
>            Priority: Major
>             Fix For: 3.4.0, 3.3.4, 3.2.10
>
>
> 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)

Reply via email to