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 Sat, 28 Jan 2017 02:43:36 GMT
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