In anticipation of the up-coming .NET Core 2.0 release (and the preview currently available), Todd, Jess, and Chris offer their answers to some of the frequently asked questions around .NET Core, such as:
Does .NET Core 2.0 have all the namespaces/APIs as .NET 4.6?
Does .NET Core support Visual Basic (VB.NET) yet?
What about SignalR - is that available?
What options do I have when running my ASP.NET Core applications? Do I have to use IIS? What about Docker?
What is .NET Standard (and should I care)?
What's the best IDE to use when building an ASP.NET Core application?And, of course…
Should I start moving from .NET 4.6 to .NET Core now? Is it ready for prime time?
Links and References
Webinar courtesy of PostSharp: Who needs Visual Studio? A look at .NET Core on Linux
Build 2017 Sessions online
An overview of .NET Core, discussing the approach, features, and goals
Visual Basic in .NET Core announced with .NET Core 2.0 Preview 1(It's there… search for "Visual Basic is now Supported" on the page)
Visual Studio 2017 Preview(Includes tooling for Visual Basic in .NET Core and .NET Core 2.0 / ASP.NET Core 2.0)
ASP.NET Core SignalR at Build (video)
ASP.NET Core SignalR Repository
ASP.NET Core Roadmap
Socket.io - Real-Time Web in Node
Anders Hejlsberg: What's New In TypeScript (video)(This turned out to be a good introduction to TypeScript and how it can help you in different ways, you can choose what you want to adopt)
Kestrel in production (internet facing) and using a reverse proxy"If you expose your application to the Internet, you must use IIS, Nginx, or Apache as a reverse proxy server."
Matt Watson from Stackify has some plain english on this on the Stackify blog(Thank you Matt!)
You will need the "ASP.NET Core Module" to run Kestrel behind IIS
Introducing .NET Standard (blog post)
.NET Standard documentation
Visual Studio for Mac