reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Douglas Service <dsop...@gmail.com>
Subject Re: Transition from .NET 4.5 to .NET Core 1.1 and .NET 4.6
Date Wed, 08 Feb 2017 22:04:01 GMT
Here is an update on the progress. It turns out that .NET Core 2.0 is now
available (https://github.com/dotnet/cli/tree/master select the master
branch as the MD file changes with the branch) and the amount of code that
we need to change in REEF is much smaller if we go to .NET Core 2.0 instead
of 1.1. With some help from .NET team we upgraded our version of the MS
Avro repository to .NET Core 2.0 and it now compiles and runs on both
Windows 10 and Ubuntu 16.04.

Thus I propose that we now target .NET Core 2.0 instead of 1.1 as it will
make the conversion go much faster and give us a larger API surface to use
in REEF.

Doug

On Mon, Jan 30, 2017 at 9:10 AM, Markus Weimer <markus@weimo.de> wrote:

> +1 on keeping the current files for now.
>
> That said, the new project file format also affords the building of .NET
> 4.5 binaries. Hence, we *could* switch to use only the new project file
> format once all of us switch to VS 2017 (once that is released). I'm fine
> with doing that, but am sure that others have concerns with moving to a new
> VS release so aggressively.
>
> Thoughts?
>
> Markus
>
> On Fri, Jan 27, 2017 at 6:43 PM, Douglas Service <dsopsrc@gmail.com>
> wrote:
>
> > Hello Julia,
> >
> > The new .NET Core 1.1 / .NET 4.6 csproj file format is not backwards
> > compatible with VS2015 and VS2013. My current understanding of the
> release
> > plan for REEF is to do one more .NET 4.5 release and then switch to .NET
> > Core 1.1 / .NET 4.6. That being the case, keeping the project files
> > separate will help prevent regressions in the current .NET 4.5 code.
> >
> > Doug
> >
> > On Tue, Jan 24, 2017 at 7:31 PM, Julia Wang (QIUHE) <
> > Qiuhe.Wang@microsoft.com> wrote:
> >
> > > Is the .NET Core  1.1 / .NET 4.6 backward compatible? Can the new
> csproj
> > > file and sln file still be opened in VS 2013 and VS2015?  If yes, why
> we
> > > have to keep old project files and use different names for new files?
> > >
> > > Thanks,
> > > Julia
> > >
> > > -----Original Message-----
> > > From: Douglas Service [mailto:dsopsrc@gmail.com]
> > > Sent: Tuesday, January 24, 2017 7:11 PM
> > > To: dev@reef.apache.org
> > > Subject: Re: Transition from .NET 4.5 to .NET Core 1.1 and .NET 4.6
> > >
> > > The NC stands for .NET Core; however, we can use another abbreviation
> if
> > > that is preferable.
> > >
> > > Doug
> > >
> > > On Tue, Jan 24, 2017 at 5:35 PM, Markus Weimer <markus@weimo.de>
> wrote:
> > >
> > > > On 2017-01-24 16:26, Douglas Service wrote:
> > > >
> > > >> Here is a the current proposal for moving from .NET 4.5 to .NET Core
> > > >> 1.1 / .NET 4.6 which will allow the C# portion of REEF to run on
> both
> > > >> Windows and Linux.
> > > >>
> > > >
> > > > Looks good to me. What does `NC` in the file names stand for?
> > > >
> > > > Thanks,
> > > >
> > > > Markus
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message