Microsoft provide a few IDEs (VS Code being cross platform too – which is a first), but which should you use for .NET Core development and how do you choose?
What are the official tooling options available when you are forced to choose between them?
Microsoft’s cloud hosting service, Azure, is really powerful. Visual Studio 2017 hooks directly into Azure, as does the .NET Core tooling. With that in mind, we’re going to publish a WebApi application to Azure and watch it fly.
Visual Studio 2107 was recently released.
In this blog post I guide you through installing it on Windows, and ways to use it even if you don’t run Windows (and don’t like the idea of dual booting or using a local VM). We’ll also build an extremely simple application together, because I’m nice like that.
Now that we’ve all got Visual Studio 2017 installed, those of us who are .NET Core developers will need to know how to convert our project.json solutions to the new csproj one. Luckily, I have you covered.
A round up of some of the bigger news items in the .NET Core SDK and relating tooling space.
Including a mention of a release date for .NET Core 2.0, changes to templating in the SDK and even Visual Studio 2017