[
https://issues.apache.org/jira/browse/TINKERPOP-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693135#comment-16693135
]
Florian Hockmann commented on TINKERPOP-2085:
---------------------------------------------
Good point. I haven't really looked at DocFX since the early days of
Gremlin.Net, but it looks like they still don't support .NET Core. They seem to
be currently mainly working on their version v3 [which supports .NET
Core|https://github.com/dotnet/docfx/issues/138#issuecomment-413128751] and
they plan to release a first version of that [at the end of this
year|https://github.com/dotnet/docfx/blob/dev/Roadmap.md#v3-timeline].
Another tool I just found with a quick search is [Wyam|https://wyam.io/], a C#
tool to generate static web content. This also [supports the generation of .NET
API docs|https://codeopinion.com/generating-c-api-documentation-with-wyam/],
but it is currently also .NET Framework only and has a similar timeline for
.NET Core, aka, a [first release in the next few
weeks|https://github.com/Wyamio/Wyam/issues/300#issuecomment-433085916].
I haven't taken a deeper look at Wyam to be able to really compare the two
tools, but DocFX seems to be the de-facto standard nowadays for .NET API docs
and Microsoft is also using it to generate the official .NET docs. So, I
currently tend to either wait for .NET Core support in DocFX or to use that now
with Mono if we want to get the docs for the next version and then later on we
probably only have to change one or two lines of code from Mono to .NET Core.
In general, I'd say that both of these tools will support .NET Core before the
issues with NuGet are resolved I mentioned in my earlier comment here. So, I
don't think that the docs generation will bind us longer to Mono than the NuGet
issues.
> Remove dependency on Mono
> -------------------------
>
> Key: TINKERPOP-2085
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2085
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release, dotnet
> Affects Versions: 3.2.10
> Reporter: Florian Hockmann
> Priority: Minor
>
> We currently rely on Mono to push NuGet packages and to create the
> Gremlin.Net.Template package.
> To push the packages, we can now also simply use [{{dotnet nuget
> push}}|https://docs.microsoft.com/dotnet/core/tools/dotnet-nuget-push]
> and for dotnet templates, there seems to be [a
> workaround|https://github.com/NuGet/Home/issues/4254#issuecomment-372795990]
> that uses a dummy {{.csproj}} file which enables {{dotnet pack}} to create a
> valid NuGet package for a dotnet template.
> So, we don't have to use Mono any more at all and we also shouldn't need to
> download nuget.exe any more during the build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
