Hey Jens, Problems with a .Net Standard lib? --Randy On Thu, Jan 3, 2019 at 10:39 AM Jens Geyer <jensge...@hotmail.com> wrote: > > Great idea. Not. > > -----Ursprüngliche Nachricht----- > From: Randy Abernethy > Sent: Thursday, January 3, 2019 7:18 PM > To: dev@thrift.apache.org > Subject: Re: Support for lib/csharp .NET Framework before 4.5? > > A .Net Standard library should work with a .NET Core app, a .NET > Framework/Mono app or a Xamarin app. I think it would be best to make > Thrift a .net standard lib exclusively. Given our lack of need for GUI > features it seems we should be easily able to comply with .Net > Standard. Probably should get rid of csharp (and and maybe netcore) > dir and merge everything (into a netstandard dir?). If .Net Framework > 4.5 support is important we could do .net Standard 1.0. For testing > netcore seems the right approach as it is likely the choice for cloud > native microservices and offers the most direct impl of the standard. > > > > On Thu, Jan 3, 2019 at 7:45 AM James E. King III <jk...@apache.org> wrote: > > > > To clarify, voting on C++03 and Cocoa ends tomorrow. > > We'll call for votes on others. > > > > If we could merge netcore into lib/csharp and have a single project > > produce > > both net45 and netstandard2.0 targets that would be ideal... I'm not sure > > how compatible the code is though. > > > > On Wed, Jan 2, 2019 at 8:34 PM Randy Abernethy <randy.aberne...@rx-m.com> > > wrote: > > > > > @jking yes /lib/netcore is the .Net Core impl, I am suggesting we > > > ultimately remove /lib/csharp, which is the .Net Framework impl. I am > > > _not_ suggesting we just del it, I am suggesting we direct all new > > > contrib to netcore and stop taking pulls for csharp and create an > > > incentive to port everything in C# missing from netcore (simple in > > > most cases I've looked at). > > > > > > On Wed, Jan 2, 2019 at 1:11 PM Allen George <allen.geo...@gmail.com> > > > wrote: > > > > > > > > So, just to be clear, proposed language removals are: > > > > > > > > Approved: > > > > > > > > Cocoa > > > > C++03 or less > > > > > > > > Open: > > > > > > > > JavaME (potential; I’ll look at setting up an Android CI environment > > > > and > > > > using the standard Java lib there to see if it’s feasible) > > > > .net 4.5 or less (no vote yet) > > > > Silverlight > > > > One of nodets/ts (can we end up only with one, or are there legitimate > > > > differences between the two was the question) > > > > > > > > Allen > > > > > > > > > > > > On January 2, 2019 at 15:55:41, Jens Geyer (jensge...@hotmail.com) > > > wrote: > > > > Hi, > > > > > > > > start a vote. A while ago some people claimed that 4.5+ was not > > > > available > > > > on > > > > their particular subset of Mono. I tend to think that this is no > > > > longer > > > the > > > > case anymore, so we should drop anything below 4.5. > > > > > > > > And since wer'e at it: Same for Silverlight, if you ask me. It is > > > > still > > > > supported until 2012 by Microsoft, but I doubt if anyone really uses > > > > it > > > > except for maintaining legacy projects. Maybe we should have a vote > > > > about > > > > that too. > > > > > > > > Have fun, > > > > JensG > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > > From: James E. King III > > > > Sent: Wednesday, January 2, 2019 9:08 PM > > > > To: dev@thrift.apache.org > > > > Subject: Re: Support for lib/csharp .NET Framework before 4.5? > > > > > > > > We already support netstandard2.0 (.NET Core SDK 2.0) and build > > > > lib/netcore and run cross tests with that. The docker build image > > > > (build/docker/ubuntu-bionic/Dockerfile) defines the version we build > > > > against. I was wondering about the .NET 3.5 in lib/csharp and > > > > whether we really need a 3.5 and a 4.5 csproj. It's not a big deal > > > > really, just a small simplification, but if a lot of people are still > > > > on > > > > .NET 3.5 then we may decide not to remove support for it yet. > > > > > > > > - Jim > > > > > > > > On Wed, Jan 2, 2019 at 12:55 PM Randy Abernethy < > > > randy.aberne...@rx-m.com> > > > > wrote: > > > > > > > > > While we're in the process of dropping old lang vers, I think we > > > > > should consider only tracking the latest version of .Net Core (2.2). > > > > > Core is CLI build friendly and cross platform. The .Net Framework > > > > > can > > > > > run all Core apps AFAIK so no loss in dropping the Framework for > > > > > forward looking stuff. > > > > > > > > > > On Wed, Jan 2, 2019 at 6:24 AM James E. King III <jk...@apache.org> > > > > wrote: > > > > > > > > > > > > We currently have two projects to support.NET 3.5 and .NET 4.5. > > > > > > The > > > > > > differences are minor but it causes us to have to build two > > > > > > projects. > > > > > > Do > > > > > > we need to continue to maintain support for .NET < 4.5 ? > > > > > > > > > > > > - Jim > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > -- > > > > > Randy Abernethy > > > > > Managing Partner > > > > > RX-M, LLC > > > > > randy.aberne...@rx-m.com > > > > > o 415-800-2922 > > > > > c 415-624-6447 > > > > > > > > > > > > > > > > > -- > > > > > > -- > > > Randy Abernethy > > > Managing Partner > > > RX-M, LLC > > > randy.aberne...@rx-m.com > > > o 415-800-2922 > > > c 415-624-6447 > > > > > > > -- > > -- > Randy Abernethy > Managing Partner > RX-M, LLC > randy.aberne...@rx-m.com > o 415-800-2922 > c 415-624-6447 >
-- -- Randy Abernethy Managing Partner RX-M, LLC randy.aberne...@rx-m.com o 415-800-2922 c 415-624-6447
