[
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964735#comment-15964735
]
ASF GitHub Bot commented on TINKERPOP-1552:
-------------------------------------------
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/600
I developed the C# project before in another repository and only used the
development branch in the end to merge it into TinkerPop. That's why it seemed
to go so quickly 😄
Do you want to figure out the test framework before merging in new GLVs or
can we merge it in and then adopt the framework later on? Maybe it's even an
advantage to have a GLV ready that is completely independent of Java for
developing the testing framework as it should be generally possible to use the
framework with other languages when it works with a .NET based GLV.
I also tried to to reach a good code coverage, but a common testing
framework for all GLVs would be really nice of course.
If you have any .NET related problems, don't hesitate to ask. But in
general I think that it is much easier to work with .NET now thanks to .NET
Core which allows to do basically everything from the command line like
building and testing and it's OS-independent.
[Rider](https://www.jetbrains.com/rider/) might also be interesting for you,
especially when you work on Linux and are used to IntelliJ.
> 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
>
> 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.3.15#6346)
