thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Geyer (JIRA)" <>
Subject [jira] [Commented] (THRIFT-4535) Current state and future of .NET libraries ("csharp" and "netcore")?
Date Fri, 30 Mar 2018 11:43:00 GMT


Jens Geyer commented on THRIFT-4535:

This sounds like a good plan! What is your policy on backwards compatibility and supported
.NET framework/platforms versions? If there were just one code base, would you still want
to support Silverlight (Official Microsoft support will end in 2021) and .NET framework versions
older than 4.5 in this new release?

Good question. Maybe we should have a poll about this, because after the next release someone
will come and complain if we throw something out, even if we announce it clearly six months
in advance (and given the current release cycle this is an understatement).

Again, I'm 100% for it (to merge netcore back into csharp) , and I would agree to dropping
support for older frameworks. We just ned to keep Mono in mind and distros like CentOS which
are not always blessed with the newest stuff. 

TL;DR: If you need any support for the task, let us know.

> Current state and future of .NET libraries ("csharp" and "netcore")?
> --------------------------------------------------------------------
>                 Key: THRIFT-4535
>                 URL:
>             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
>  * The "csharp" project does not target ".NET Standard" and there's only a very old release
on ( if [] is the official one).
>  * The "netcore" project does target ".NET Standard" but there's no release yet ( ) and
it also has a dependency on ASP.NET Core ( )
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 

This message was sent by Atlassian JIRA

View raw message