News for hackers. Stuff that matters.

A comment on Introducing .NET Standard. Parent comment

Re:Introducing .NET Standard by yazr on Monday September 26, 2016 @03:57PM (#12585044)
R U saying that (currently) Mono is a superset of Core ?

So i am starting with a large and varied Win code base, i will have an easier time porting (as much of it as possible) to Mono rather than Core ?

[ Parent | on HN ]
Re:Introducing .NET Standard by rodrigokumpera on Tuesday September 27, 2016 @02:54AM (#12587887)
MS engineer here, I work on mono.

Mono is not a strict superset of .net Core. We follow desktop more closely.

The extra APIs that are part of .net core, and are features on .net standard 1.6 will come to mono as we get the time to implement them.

[ Parent | on HN ]
Re:Introducing .NET Standard by aandrieiev on Tuesday September 27, 2016 @04:03AM (#12588064)
Is mono going to be fully merged into .net _something_ (core? standard?) at some point in the future or it will remain separate?
[ Parent | on HN ]
Re:Introducing .NET Standard by WorldMaker on Monday September 26, 2016 @04:14PM (#12585158)
Mono is not a direct superset of Core, but yes if you have an existing large .NET application you might have an easier time working with Mono than Core. Some of that may change as Core starts to get closer to .NETSTandard 2.0, depending on what sort of a legacy codebase you refer to. (That is, Mono has an okay-not-great emulation library for System.Windows.Forms, but it seems like it may be unlikely for .NET Core to have anything similar.)
[ Parent | on HN ]