You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Markus Weimer <ma...@weimo.de> on 2017/04/20 15:48:11 UTC
We have our first .NET Core project!
Hi,
thanks to Scott, we now have our first .NET Core project in the code
base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
Markus
[0]: https://github.com/apache/reef/pull/1279
Re: We have our first .NET Core project!
Posted by Douglas Service <ds...@gmail.com>.
You can move forwards on removing incompatibilities.
On Fri, Apr 21, 2017 at 2:46 PM, Saikat Kanjilal <sx...@gmail.com> wrote:
> Understood, what I am really wondering about is whether it makes sense to
> wait till Scott finishes before any of the portability analyzer efforts
> continue, that way I can just start with the new project files we need to
> use to move forward, what do you think, I can in the meantime help Sergiy
> with reef<->reef efforts.
>
> On Fri, Apr 21, 2017 at 1:46 PM, Douglas Service <ds...@gmail.com>
> wrote:
>
> > REEF-1578 brings in the first .NET Core VS 2017 project file which allows
> > REEF utilities to compile to .NET Standard 2.0, .NET 4.5.1, and .NET 4.6.
> > There is overlap between what you and and Scott are doing in the sense
> that
> > any incompatibilities in existing REEF code with .NET Core/Standard 2.0
> and
> > .NET 4.6 must removed in order for the new project files can be used to
> > complete a successful compilation to one of the new targets. I created
> the
> > issues your are working on when we thought the target would be .NET
> > Core/Standard 1.1 and .NET 4.6 so the attached analyzer files are out of
> > date and you need to rerun against .NET Core/Standard 2.0, 4.5.1, and
> 4.6.
> >
> > Doug
> >
> > On Thu, Apr 20, 2017 at 1:35 PM, Saikat Kanjilal <sx...@gmail.com>
> > wrote:
> >
> > > Markus/Scott/Doug,
> > > I am diving back into reef to also help out on reef-1583, its not clear
> > to
> > > me that the fixes that were applied to REEF-1578 have anything to do
> with
> > > fixing the portability analyzer issues that I've been working on
> (namely
> > > REEF-1584 through REEF-1588). I was wondering if 1578 was attempted
> to
> > > address the portability analyzer issues, if not we should talk further
> > > about merging the two different efforts between Scott and myself at
> some
> > > point?
> > >
> > > Thoughts?
> > >
> > > On Thu, Apr 20, 2017 at 8:48 AM, Markus Weimer <ma...@weimo.de>
> wrote:
> > >
> > > > Hi,
> > > >
> > > > thanks to Scott, we now have our first .NET Core project in the code
> > > > base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
> > > >
> > > > Markus
> > > >
> > > > [0]: https://github.com/apache/reef/pull/1279
> > > >
> > >
> >
>
Re: We have our first .NET Core project!
Posted by Saikat Kanjilal <sx...@gmail.com>.
Hey Rogan,
Feel free to take a look at any of the JIRA's I mention below that are assigned to me to start, let me know so that we don't duplicate efforts.
Thanks
Sent from my iPhone
> On Apr 21, 2017, at 3:23 PM, Rogan Carr <ro...@gmail.com> wrote:
>
> Hi All,
>
> I'd love to help out with the REEF.NET on Linux / CoreCLR work too. Are
> there any issues that I could focus on?
>
> Best,
> Rogan
>
>> On Fri, Apr 21, 2017 at 2:46 PM, Saikat Kanjilal <sx...@gmail.com> wrote:
>>
>> Understood, what I am really wondering about is whether it makes sense to
>> wait till Scott finishes before any of the portability analyzer efforts
>> continue, that way I can just start with the new project files we need to
>> use to move forward, what do you think, I can in the meantime help Sergiy
>> with reef<->reef efforts.
>>
>> On Fri, Apr 21, 2017 at 1:46 PM, Douglas Service <ds...@gmail.com>
>> wrote:
>>
>>> REEF-1578 brings in the first .NET Core VS 2017 project file which allows
>>> REEF utilities to compile to .NET Standard 2.0, .NET 4.5.1, and .NET 4.6.
>>> There is overlap between what you and and Scott are doing in the sense
>> that
>>> any incompatibilities in existing REEF code with .NET Core/Standard 2.0
>> and
>>> .NET 4.6 must removed in order for the new project files can be used to
>>> complete a successful compilation to one of the new targets. I created
>> the
>>> issues your are working on when we thought the target would be .NET
>>> Core/Standard 1.1 and .NET 4.6 so the attached analyzer files are out of
>>> date and you need to rerun against .NET Core/Standard 2.0, 4.5.1, and
>> 4.6.
>>>
>>> Doug
>>>
>>> On Thu, Apr 20, 2017 at 1:35 PM, Saikat Kanjilal <sx...@gmail.com>
>>> wrote:
>>>
>>>> Markus/Scott/Doug,
>>>> I am diving back into reef to also help out on reef-1583, its not clear
>>> to
>>>> me that the fixes that were applied to REEF-1578 have anything to do
>> with
>>>> fixing the portability analyzer issues that I've been working on
>> (namely
>>>> REEF-1584 through REEF-1588). I was wondering if 1578 was attempted
>> to
>>>> address the portability analyzer issues, if not we should talk further
>>>> about merging the two different efforts between Scott and myself at
>> some
>>>> point?
>>>>
>>>> Thoughts?
>>>>
>>>> On Thu, Apr 20, 2017 at 8:48 AM, Markus Weimer <ma...@weimo.de>
>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> thanks to Scott, we now have our first .NET Core project in the code
>>>>> base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
>>>>>
>>>>> Markus
>>>>>
>>>>> [0]: https://github.com/apache/reef/pull/1279
>>>>>
>>>>
>>>
>>
Re: We have our first .NET Core project!
Posted by Rogan Carr <ro...@gmail.com>.
Hi All,
I'd love to help out with the REEF.NET on Linux / CoreCLR work too. Are
there any issues that I could focus on?
Best,
Rogan
On Fri, Apr 21, 2017 at 2:46 PM, Saikat Kanjilal <sx...@gmail.com> wrote:
> Understood, what I am really wondering about is whether it makes sense to
> wait till Scott finishes before any of the portability analyzer efforts
> continue, that way I can just start with the new project files we need to
> use to move forward, what do you think, I can in the meantime help Sergiy
> with reef<->reef efforts.
>
> On Fri, Apr 21, 2017 at 1:46 PM, Douglas Service <ds...@gmail.com>
> wrote:
>
> > REEF-1578 brings in the first .NET Core VS 2017 project file which allows
> > REEF utilities to compile to .NET Standard 2.0, .NET 4.5.1, and .NET 4.6.
> > There is overlap between what you and and Scott are doing in the sense
> that
> > any incompatibilities in existing REEF code with .NET Core/Standard 2.0
> and
> > .NET 4.6 must removed in order for the new project files can be used to
> > complete a successful compilation to one of the new targets. I created
> the
> > issues your are working on when we thought the target would be .NET
> > Core/Standard 1.1 and .NET 4.6 so the attached analyzer files are out of
> > date and you need to rerun against .NET Core/Standard 2.0, 4.5.1, and
> 4.6.
> >
> > Doug
> >
> > On Thu, Apr 20, 2017 at 1:35 PM, Saikat Kanjilal <sx...@gmail.com>
> > wrote:
> >
> > > Markus/Scott/Doug,
> > > I am diving back into reef to also help out on reef-1583, its not clear
> > to
> > > me that the fixes that were applied to REEF-1578 have anything to do
> with
> > > fixing the portability analyzer issues that I've been working on
> (namely
> > > REEF-1584 through REEF-1588). I was wondering if 1578 was attempted
> to
> > > address the portability analyzer issues, if not we should talk further
> > > about merging the two different efforts between Scott and myself at
> some
> > > point?
> > >
> > > Thoughts?
> > >
> > > On Thu, Apr 20, 2017 at 8:48 AM, Markus Weimer <ma...@weimo.de>
> wrote:
> > >
> > > > Hi,
> > > >
> > > > thanks to Scott, we now have our first .NET Core project in the code
> > > > base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
> > > >
> > > > Markus
> > > >
> > > > [0]: https://github.com/apache/reef/pull/1279
> > > >
> > >
> >
>
Re: We have our first .NET Core project!
Posted by Saikat Kanjilal <sx...@gmail.com>.
Understood, what I am really wondering about is whether it makes sense to
wait till Scott finishes before any of the portability analyzer efforts
continue, that way I can just start with the new project files we need to
use to move forward, what do you think, I can in the meantime help Sergiy
with reef<->reef efforts.
On Fri, Apr 21, 2017 at 1:46 PM, Douglas Service <ds...@gmail.com> wrote:
> REEF-1578 brings in the first .NET Core VS 2017 project file which allows
> REEF utilities to compile to .NET Standard 2.0, .NET 4.5.1, and .NET 4.6.
> There is overlap between what you and and Scott are doing in the sense that
> any incompatibilities in existing REEF code with .NET Core/Standard 2.0 and
> .NET 4.6 must removed in order for the new project files can be used to
> complete a successful compilation to one of the new targets. I created the
> issues your are working on when we thought the target would be .NET
> Core/Standard 1.1 and .NET 4.6 so the attached analyzer files are out of
> date and you need to rerun against .NET Core/Standard 2.0, 4.5.1, and 4.6.
>
> Doug
>
> On Thu, Apr 20, 2017 at 1:35 PM, Saikat Kanjilal <sx...@gmail.com>
> wrote:
>
> > Markus/Scott/Doug,
> > I am diving back into reef to also help out on reef-1583, its not clear
> to
> > me that the fixes that were applied to REEF-1578 have anything to do with
> > fixing the portability analyzer issues that I've been working on (namely
> > REEF-1584 through REEF-1588). I was wondering if 1578 was attempted to
> > address the portability analyzer issues, if not we should talk further
> > about merging the two different efforts between Scott and myself at some
> > point?
> >
> > Thoughts?
> >
> > On Thu, Apr 20, 2017 at 8:48 AM, Markus Weimer <ma...@weimo.de> wrote:
> >
> > > Hi,
> > >
> > > thanks to Scott, we now have our first .NET Core project in the code
> > > base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
> > >
> > > Markus
> > >
> > > [0]: https://github.com/apache/reef/pull/1279
> > >
> >
>
Re: We have our first .NET Core project!
Posted by Douglas Service <ds...@gmail.com>.
REEF-1578 brings in the first .NET Core VS 2017 project file which allows
REEF utilities to compile to .NET Standard 2.0, .NET 4.5.1, and .NET 4.6.
There is overlap between what you and and Scott are doing in the sense that
any incompatibilities in existing REEF code with .NET Core/Standard 2.0 and
.NET 4.6 must removed in order for the new project files can be used to
complete a successful compilation to one of the new targets. I created the
issues your are working on when we thought the target would be .NET
Core/Standard 1.1 and .NET 4.6 so the attached analyzer files are out of
date and you need to rerun against .NET Core/Standard 2.0, 4.5.1, and 4.6.
Doug
On Thu, Apr 20, 2017 at 1:35 PM, Saikat Kanjilal <sx...@gmail.com> wrote:
> Markus/Scott/Doug,
> I am diving back into reef to also help out on reef-1583, its not clear to
> me that the fixes that were applied to REEF-1578 have anything to do with
> fixing the portability analyzer issues that I've been working on (namely
> REEF-1584 through REEF-1588). I was wondering if 1578 was attempted to
> address the portability analyzer issues, if not we should talk further
> about merging the two different efforts between Scott and myself at some
> point?
>
> Thoughts?
>
> On Thu, Apr 20, 2017 at 8:48 AM, Markus Weimer <ma...@weimo.de> wrote:
>
> > Hi,
> >
> > thanks to Scott, we now have our first .NET Core project in the code
> > base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
> >
> > Markus
> >
> > [0]: https://github.com/apache/reef/pull/1279
> >
>
Re: We have our first .NET Core project!
Posted by Saikat Kanjilal <sx...@gmail.com>.
Markus/Scott/Doug,
I am diving back into reef to also help out on reef-1583, its not clear to
me that the fixes that were applied to REEF-1578 have anything to do with
fixing the portability analyzer issues that I've been working on (namely
REEF-1584 through REEF-1588). I was wondering if 1578 was attempted to
address the portability analyzer issues, if not we should talk further
about merging the two different efforts between Scott and myself at some
point?
Thoughts?
On Thu, Apr 20, 2017 at 8:48 AM, Markus Weimer <ma...@weimo.de> wrote:
> Hi,
>
> thanks to Scott, we now have our first .NET Core project in the code
> base. O.A.R.Utilities produces a .NET Standard 2.0 DLL now [0].
>
> Markus
>
> [0]: https://github.com/apache/reef/pull/1279
>