reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <>
Subject [jira] [Updated] (REEF-1583) Upgrade REEF.NET to requite .NET 4.5.1
Date Thu, 30 Mar 2017 21:50:41 GMT


Markus Weimer updated REEF-1583:
    Summary: Upgrade REEF.NET to requite .NET 4.5.1  (was: Fix CoreCLR issues in Org.Apache.REEF.Network,
also upgrade all .net projects to use .net framework 451 as part of this)

> Upgrade REEF.NET to requite .NET 4.5.1
> --------------------------------------
>                 Key: REEF-1583
>                 URL:
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF.NET
>            Reporter: Doug Service
>            Assignee: Saikat Kanjilal
>            Priority: Blocker
>              Labels: CoreCLR, [Breaking]
>             Fix For: 0.16
>         Attachments: PortabilityAnalysis.html
> We are expanding this JIRA to do an across the board upgrade for all visual studio projects
to use .net framework 451
> This JIRA issue's goal is to have the Org.Apache.REEF.Network project work with .net
standard 2.0, in order to do this we are evaluating whether or not to do the upgrade to .net
framework 451:
> What needs to be done to moving to .net framework 451?
> - Upgrade the Org.Apache.Reef.Network project to use 451
> - Figure out what other dependent projects need upgrading as well
> - No need to use my custom cache, we can try to move forward with Microsfot.Extensions.Memory.MemoryCache
> - Do a deep analysis on the ramifications on making this upgrade across all of the codebase,
do we need to fix unit/integration tests as well
> - Refactor the code to get past the portability analyzer warnings (yes this will occure
even after upgrading to 451)
> What if we don't upgrade
>  - I've attached a pull request to REEF-1583, we can use my custom in memory cache, it
works as far as unit tests are concerned , will need to figure out if we need additional integration
tests, this is needed as the original MemoryCache APIs will not work with .net standard 2.0
as well as .net framework 451
> - If we go this route I will need to fix the other portability analyzer warnings by not
upgrading other parts of the code as well

This message was sent by Atlassian JIRA

View raw message