reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rogan Carr <rogan.c...@gmail.com>
Subject Re: REEF-1817: Fix CoreCLR issues in REEF.Common
Date Thu, 06 Jul 2017 00:03:19 GMT
Hi All,

Quick question on CoreCLR Compatibility: For REEF.NET, we just need .NET
Standard 2.0, .NET Core 2.0 for DLLs, right? Am I correct that only
executables need ".NET Core + Platform Extensions 1.0"?

Thanks for your help!

Best,
Rogan

On Wed, Jul 5, 2017 at 4:57 PM, Rogan Carr <rogan.carr@gmail.com> wrote:

> Hi All,
>
> REEF.Common may be a bit more difficult to convert, as it uses a library,
> PerformanceCounters, that is not available in the CLR (see my comments on
> 1817 [1]). I'll investigate more to see what the impact will be.
>
> In the meantime, I created REEF-1821 to fix CoreCLR compatibility issues
> that arise from using non-compliant exceptions [2].
>
> Best,
> Rogan
>
> [1] https://issues.apache.org/jira/browse/REEF-1817
> [2] https://issues.apache.org/jira/browse/REEF-1821
>
> On Thu, Jun 29, 2017 at 4:05 AM, Byung-Gon Chun <bgchun@gmail.com> wrote:
>
>> Welcome, Rogan!
>>
>> On Thu, Jun 29, 2017 at 11:02 AM, Markus Weimer <markus@weimo.de> wrote:
>>
>> > Welcome to the team, Rogan! The plan you mention makes sense. -- Markus
>> >
>>
>>
>>
>> --
>> Byung-Gon Chun
>>
>
>

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