Great stuff, I love seeing what people are building with .NET Core. I feel like I'm getting much closer to the point that I could confidently commit to building a greenfields project for a client in it.
Are there any parts of the project you could highlight as being much harder or easier as a result of building it in .NET Core over, say, .NET 4.6?
Adopting and porting to .NET Core will become a ton easier, later this year. .NET Core 2.0 will add a ton of .NET Framework APIs.
These APIs are almost entirely coming from .NET Standard 2.0. See the jump in APIs in this table[1].
We often get asked if this is going against the promise of a light-weight development platform. Answer: not really. The new APIs are not being added to a single library, but several, including new ones. We will be updating our publishing tools to make it easier publish apps w/only the libraries you need. We are also looking at going one step further, which is publishing only the IL you need (intra-assembly optimization).
I am spending the week presenting at two Microsoft conferences in Europe (Milan, Amsterdam). I heard very similar feedback on EF yesterday in Milan. I will be passing this off to the EF team.
Are there any parts of the project you could highlight as being much harder or easier as a result of building it in .NET Core over, say, .NET 4.6?