reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saikat Kanjilal <>
Subject Re: location of documentation
Date Wed, 01 Mar 2017 20:54:04 GMT
To bring in down to more specifics, here's the class causing issues (
The warning messages are associated with the various APIs for this class
and they all say Not supported on .NET Framework=v4.5;.NET Standard
Version=2.0.    This seems to imply that several APIs from this class will
change, @Scott/Doug/Markus when you guys run into this type of a warning
message do you: 1) ignore and fix later in most cases 2) figure out a
workaround with the constraints of .NET v4.5/.NET STandard 2.0.  I'd just
like to understand how you guys have been tackling these types of warnings
so I take a consistent approach.

On Wed, Mar 1, 2017 at 8:52 AM, Markus Weimer <> wrote:

> On 2017-02-28 16:14, Saikat Kanjilal wrote:
>> I am seeing a bunch of APIs around one or two classes that are no
>> longer supported in .NET Standard 2.0 using .Net Framework 4.5.  At
>> this point we can move forward in several ways: a) use a different
>> class that essentially does the same thing but is supported under
>> .Net Standard 2.0 b) ignore these for now and add TODO's with
>> comments.
> If there is a workaround that works in .NET 4.5, we should use it.\
> Any recommendations, also is there a central place to go to see what
>> classes are available as interfaces in .net standard 2.0
> Not that I am aware off. .NET Standard 2.0 isn't released yet. Hence,
> I'd hope for this to become available at a later time, as part of the
> release.
> Markus

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