azure

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

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

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

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

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