[
https://issues.apache.org/jira/browse/THRIFT-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420427#comment-16420427
]
James E. King, III commented on THRIFT-4535:
--------------------------------------------
Folks stuck needing to support older frameworks like .NET 3.5.1 can continue to
use Thrift 0.11.0 or earlier. We shouldn't be scared to drop older language
support because folks can continue to use older Thrift to make it work. One
can use Thrift 0.7.0 client with a Thrift 0.11.0 server, for example, if it
were truly necessary to support some ancient language level. So if you are
using an older CentOS with an older mono, you might need to use an older
thrift. That's reasonable.
This is an incredibly complex product and we need to think really hard about
how far back we support languages and what that means to our ability to improve
the code for each language. There was a breaking change between go 1.6 and 1.7
that we had to do a lot of work to support... however as of February 2018,
support for go 1.8 was dropped by the golang project. We should not have to
support golang 1.8 or earlier, and I instructed folks as such in a PR where
that came into question. I'f quite sure anyone using go in production is
regularly updating based on the golang project's aggressive EoL strategy. If
they are not, well, they are asking for trouble.
For csharp I would expect us to be supporting .NET Framework 4.5.2 or later at
this point, based on Microsoft's support policy. It looks like we're still
checking in static visual studio and/or dotnet project files with our code
today so those have to be updated, even though I would prefer that we generate
the projects (using cmake) instead, since that is much more flexible, but we
can't really pull the trigger on that until everything builds in cmake. As
long as we can have a single set of project files that will work both for,
let's say, Visual Studio 2015 OR for dotnet core 2.0 (msbuild) on linux or
windows, then okay. If the project files are incompatible, they should
probably remain separate.
And of course by "supporting" I mean we make a best effort to prove that things
work with that language level through our CI and cross test infrastructure.
This is all FOSS, so the notion of being "supported" at all is a best-effort
community driven exercise.
For folks using mono today, I would highly recommend they start converting to
dotnet core.
> 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)
