Dipping the toe in the Azure Compute space and then some.
Over the last couple of weeks, I've just skimmed the areas of ARM templates, CLI, Docker on Linux, Azure Functions and AppService Web Apps. Check out these articles and let me know if there is something you'd like to see more on; there's a ton to talk about to solve any solution.
Visual Studio 2017 has been released and the features are great for Windows developers. However along with it comes .NET Core 1.0 tooling and large improvements to the command line experience for macOS and Linux users developing ASP.NET Core applications. One of the prevalent features shown off in VS 2017 is the Docker support and capabilities to push to Azure App Service. Using the Azure CLI 2.0, Docker and.NET CLI these same capabilities can be accomplished without friction and with just as much success and satisfaction.
I'm a very big fan of CLI tooling. If I can fire up a bash prompt and get started, you've won me over. The .NET Core team continues to improve the command line tooling experience for all platforms with dotnet new and if you're pushing your apps to the cloud; the Azure 2.0 CLI is on point for getting stuff done.
A new feature (preview) in Azure Functions is API Definition. This feature allows you to use the OpenAPI specification (aka Swagger) to document the functionality of your functions and/or endpoints.
When using the CLI to create resources there are occasions, usually when putting together a project or demo, when there are parameters that should be assumed or defaulted. This article shows how to accomplish this task.
Using the proxies feature in Azure Functions to mask unreadable URLs for your OpenAPI Specification (Swagger) to something more consumable.
Shows how to use the Swagger-UI Docker Image and host your own version in AppService for your applications Swagger. Can be used for Web API apps or Azure Functions.
Converting an ASP.NET Core Web API Application Architecture w/ Swagger Help Pages to us Azure Functions, Proxies, Docker on AppService (Linux).