Shayne Boyer

Hi, I'm Shayne Boyer, work as a developer advocate for Azure, .NET Core and Open Source, speak at national & community events while helping teams architect web and cloud applications.

Deploying WCF and .NET Core applications to a single Kubernetes cluster

In my previous post, I showed how to take a WCF service and containerize it using Visual Studio. By doing so, this gives us the opportunity to push our heritage (aka legacy) application to the cloud either in Azure App Service using Web App for Containers, Azure Container Instances (ACI), or in the event we need something like an orchestrator Kubernetes is available in AKS. Many times we would like to use the new technology with the old. For instance, creating a .NET Core Razor Pages application or .NET Core Web API to consume the WCF application. However, the new applications will be using Linux containers and everything must be scalable and run in a Kubernetes cluster. Let's see how...


Modernizing WCF Services with containers and Visual Studio

There are a number of reasons for moving long-standing .NET Framework applications like WCF, and ASP.NET Webforms to containers and then into containers or "modernizing legacy heritage apps". DevOps - Once the application is set up in a container, build a CI/CD pipeline to build and push the applications to the cloud in a streamlined fashion. Velocity - In addition to the CI/CD features, the ability to version the container, ease of deployment and rollback in the event of failures is easier. Leverage other cloud services - Add Application Insights or logging, managed database services, and other PAAS offerings.  Where to start Visual Studio 2019 has the Docker tooling built into the workloads. You will need to...


Build the code, thank the contributors!

The GitHub event announced a great new feature - GitHub Sponsors. GitHub Sponsors is a new way to financially support the developers who build the open source software you use every day. See the full announcement blog post for more information. Recognizing Contributors Recently, Brian Clark introduced me to all-contributors (https://github.com/all-contributors/all-contributors) an awesome way to recognize contributors to your project. The installation is super easy. Enable the bot on your repository, and you're ready to go. Good practice is to have a CONTRIBUTING.md in your repo not only to encourage good practices but to also set expectations and standards. Adding contributors There are a few ways in which our contributors get added to the table...


Auto blogging Jekyll with Logic Apps, ACI Containers and .NET Core

All related links: https://www.theurlist.com/autobloggerpost Jekyll is a very popular way to host a static site on GitHub and posting new content is a simple as creating a markdown file and then committing it to the relative repo. GitHub takes care of the rest. See the help pages at GitHub -> Setting up your GitHub Pages site locally with Jekyll This seemed like a great way for me to get started on a blog for some content that was being stored in a CMS. The view we are interested in is updated once a week and is accessible via .NET Standard API. There are a few options for making this happen. I could write a console application...


dotnet-azure : A .NET Core global tool to deploy an application to Azure in one command

The options for pushing your .NET Core application to the cloud are not lacking depending on what IDE or editor you have in front of you. Visual Studio has a rich GUI interface with choices to pick pursuant to the architecture of your app - Web, Containers, SQL Server, Registries, etc.; and for years has excelled at delivering a full experience. VS Code offers a great Azure extension pack and in its own fashion delivers an experience to publish your web application directly to an AppService, Container and/or Registry too. If the command line experience is more your "thing", the Azure CLI is available and any resource publish option can be had through the az command. But what if...