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.

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...


Finding your next .NET Open Source project using the command line

Many years ago I wanted to jump into a project in open source but had no idea where to start. I had worked with node.js, .NET and some other web-based technology but wasn't sure where to start and GitHub was new to me. Ironically, I fell onto Omnisharp and the .NET Core yo aspnet projects through my Microsoft MVP Summit meetings that year. Flicking through Twitter, as one does, I came across an announcement from a friend Tierny (@bitandbang) where he had started a CLI tool for node.js projects called "good-first-issue" to find random GitHub Issues for projects submitted to his tool. There are a ton of open source projects asking for help on issues that have a...


Using ASP.NET Core with MongoDB in containers for local dev, CosmosDB for production

If nothing else is true, containers have made local development on a platform so much easier. If you want to use SQL Server for your backend just docker pull microsoft/mssql-server-linux and you can start up an instance with a few parameters. Azure CosmosDB is not available as a container, however, MongoDB is available and happens to be a database I have used in previous applications. MongoDB is one of the many APIs that CosmosDB supports; locally I can develop against an instance of Mongo either in a container or installed and simply change the connection string for my production instance. The flexibility of being able to use MongoDB and then just changing a connection string to use CosmosDB is...