As I understand it, ,net standard 2.0 is now expected to contain about 30
API additions (made in 1.5 and 1.6) that are not actually available if the
runtime environment is .Net 4.6.1.

On the one hand, no need to target 4.6.2 unless we actually plan to use any
of the new API, which I don't think we are (there's not much). So we could
just as well lower it to 4.6.1.

Then, as for actually targetting .net standard 2.0 when that's available,
the work required will not depend on the difference between 4.6.1 and
4.6.2, but rather on what parts of .Net Framework (4.6.x) we use that are
NOT available in .net standard 2.0, no matter when they were introduced.
With all the additions they are making in 2.0 it's starting to look a lot
better. The large used but missing parts are System.Transactions,
CodeDom/Reflection.Emit, and hardcoded references to the SQL Server and
ODBC ADO.Net providers (for those we could use reflection as is already
done for most other providers).

Running apiport on the various assemblies (master as of 2016-11-30 or so)
reveals:
Assembly Target Framework .Net Standard,Version=v1.6 .Net
Standard,Version=v2.0
Antlr3.Runtime
88,68 99,25
Iesi.Collections
97,98 100
NHibernate .NETFramework,Version=v4.6.2 69,55 91,58
Remotion.Linq
79,82 100
vshost .NETFramework,Version=v4.0 100 100

So it's starting to look good.

2016-12-02 1:19 GMT+00:00 <[email protected]>:

> With the slightly confusing information on the upcoming .net standard 2.0
> targeting compatibility with .net 4.6.1, not 4.6.2, wouldn't it be better
> to restrict the update to .net 4.6.1 instead?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nhibernate-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Attachment: ApiPortAnalysis.xlsx
Description: MS-Excel 2007 spreadsheet

Reply via email to