[
https://issues.apache.org/jira/browse/THRIFT-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420612#comment-16420612
]
James E. King, III commented on THRIFT-4535:
--------------------------------------------
I would agree that netcore came into play because dotnet was new and I'm not
entirely sure it was all compatible with older projects as they rolled out the
technical previews, and IIRC the build process for dotnet preview was quite
different than it is now. Sounds like we're aligned; let's get everything
building inside "csharp" and carry whatever good functionality over from
netcore we can, but attempt to leave the interfaces in csharp alone if at all
possible to avoid clients needing massive rewrites. Anything you can
contribute in this space will be greatly appreciated. I know we need to get a
handle on the nuget distributions. We could also work on releasing older nuget
packages for older releases, possibly, but I would prefer to focus on getting
an official 0.12.0 out there based on the work discussed here.
The linux CI build will use mono to build the csharp environment today and will
use dotnet build to build the netcore environment. What we could do as part of
a merge here is to have the ubuntu-xenial (LTS 16.04) build environment use
only mono, and have the ubuntu-artful (which will become ubuntu-bionic when LTS
is released and I have time to support it) environment use dotnet-sdk to build
it, and that would give us coverage.
The windows CI build does not currently build either the "csharp" or the
"netcore" projects, sadly.
> Current state and future of .NET libraries ("csharp" and "netcore")?
> --------------------------------------------------------------------
>
> Key: THRIFT-4535
> URL: https://issues.apache.org/jira/browse/THRIFT-4535
> Project: Thrift
> Issue Type: Question
> Components: C# - Library, netcore - Library
> Reporter: Christian Weiss
> Priority: Major
>
> Hi,
> We are trying to use Thrift in one of our projects but we ran into some very
> fundamental issues:
> * The "csharp" project does not target ".NET Standard" and there's only a
> very old release on nuget.org ( if [https://www.nuget.org/packages/Thrift/]
> is the official one).
> * The "netcore" project does target ".NET Standard" but there's no release
> yet ( https://issues.apache.org/jira/browse/THRIFT-4512 ) and it also has a
> dependency on ASP.NET Core (
> https://issues.apache.org/jira/browse/THRIFT-4534 ) which makes it unusable
> in non-web projects.
> I'm wondering why there even are 2 separate projects for .NET? It's important
> to understand that ".NET Core" is not a new programming API - It's just a new
> platform - very similar to Silverlight, Mono, Windows Phone. This means that
> it would also be possible to support .NET Core and the new ".NET Standard"
> (which represents a common set of APIs for all platforms) with the existing
> "csharp" project.
> Was this a deliberate decision - e.g. to make the "netcore" code the official
> successor of the "csharp" code?
> Would you be interested in merging the code back into one library? I'd be
> willing to help if you want!
> It would be great to get one proper, up to date and official .NET library
> soon as there's already quite a lot of weird forks on NuGet.org:
> https://www.nuget.org/packages?q=Thrift
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
