Target .NET4.6 or .NET Core 1 for greenfield development?
<p>I'm starting to understand the naming conventions for the .NET stack cross-platform.
Particularly this page explained it well:
<a href="http://blog.tonysneed.com/2016/01/22/ef6-asp-net-core-mvc6/" rel="nofollow">http://blog.tonysneed.com/2016/01/22/ef6-asp-net-core-mvc6/</a></p>

<p>I'm starting a personal project which will be completely greenfield and see it as an opportunity to learn all these new technologies.  However, I want to re-use code from other MVC5 applications that use well known libraries.  Especially for the infrastructure &amp; plumbing I used some well-known libraries such as StructureMap, AutoMapper and for data persistance EF (EF 4/5).</p>

<p>Since there is no restriction on what version I should use, should I start from scratch and use the latest ASP.NET Core 1.0, .NET Core 1.0 along with EF Core 1.0 or is the only advantage from using only that it will be cross-platform?  In other words, if I am never going to run this on anything but Windows AND want minimum pain with library incompatibilities do I stick with .NET4.6?</p>

<p>I basically want to use this opportunity to be able to learn the new stuff without impacting on future portability for my application.  <strong>Will MS eventually make .NET Core 1 the default even on Windows?</strong></p>