Long live .Net/core.
However in getting there Microsoft have been left people a little confused.
The future is bright, the future is .Net core.
Like Gáspár Nagy has stated in his blog post https://medium.com/@gasparnagy/net-core-in-the-focus-of-c-renaissance-227ad8f59108#.ybx122a54 Bad communication of goals and status - It would be interesting to make a poll among active .NET developers with regard to the status of the .NET Core, asking questions like:
- “Has .NET Core been released already?”
- “Has ASP.NET Core been released already?”
- “Does ASP.NET Core work exclusively on .NET Core?”
- “Is .NET Core the next version of .NET?”
For instance, they've gotten rid of project.json (out with the new, in with the old) in favour of a more backwards compatible MSBuild ready, csproj format.
I personally think Microsoft should have stood their ground, been brave, and said no to backwards compatibility. If people want to migrate, give them a tool to convert it, and a report of things that are not compatible, or a list of warnings/errors in VS.
Like all good games of rugby, Microsoft will score a try eventually, and everyone will be like "yeah, C# and .Net Core is the shit, golang/pyton/java is so yesterday".
Further reading by: