[
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062636#comment-16062636
]
Jorge Bay commented on TINKERPOP-1552:
--------------------------------------
[Support for .NET Core projects on msbuild is quite
new|https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/]
so its not easy to find good docs and there are few people with experience on
the matter.
1: It looks like {{<summary>}} tag is deprecated:
https://github.com/NuGet/Home/issues/4587#issuecomment-288913324
2: You can save your api key using {{nuget}} tool:
http://blog.davidebbo.com/2011/03/saving-your-api-key-with-nugetexe.html
About 3 and 4, we could generate the csproj file as well to set the version. I
did something similar on the JavaScript GLV
https://github.com/apache/tinkerpop/blob/392c1f9c45b822c3fa7977b436f1ba4be25993df/gremlin-javascript/src/main/groovy/org/apache/tinkerpop/gremlin/javascript/GenerateGremlinJavascript.groovy#L27-L31
, when {{"SNAPSHOT"}} is present, we could generate {{x.y.z-dev<TIMESTAMP>}}
like {{3.2.5-dev20170626}}
> C# Gremlin Language Variant
> ---------------------------
>
> Key: TINKERPOP-1552
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1552
> Project: TinkerPop
> Issue Type: Improvement
> Components: language-variant
> Affects Versions: 3.2.3
> Reporter: Jorge Bay
> Assignee: stephen mallette
>
> It would be nice to have a C# GLV that runs under .NET Framework 4.5+ and
> .NET Core.
> The maven build could use the Exec Maven Plugin to exec .NET Core's [dotnet
> test|https://www.microsoft.com/net/core#macos] command.
> Some requirements, from the mailing list (edited):
> {quote}
> 1. The GLV should keep in line with class/method names of the java API
> where possible to ensure consistency of feel across languages.
> 2. There needs to be adequate tests (we're still discussing the approach to
> testing GLVs and i think that needs to be tackled sooner than later as more
> GLVs start to come in). Those tests should produce xunit style output
> unless there is some good reason not to.
> 3. There needs to be adequate documentation (e.g. Reference docs)
> 4. The build/deploy process needs to be bound to maven which might be one of
> the trickier bits to deal with.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
