docker

Modernizing legacy apps has become the theme towards the end of this year or also known as "Lift and Shift". This means taking the monolithic applications built with blood, sweat, and tears and now move them to the cloud. Nerd Dinner (https://nerddinner.codeplex.com/) is an MVC application written back in 2010, the last edit was ~Sept 6, 2013 to the mvc4 branch. I grabbed the mvc branch and copied it over to https://github.com/spboyer/nerddinner-mvc4 and fired it up in Visual Studio 2017. The plan: Migrate the LocalDB to SQL Server in Azure Using the Docker tools in Visual Studio 2017, add the Docker files Publish Docker Images to Azure Container Registry (ACR) Push the new...

Figuring out the best way to build and deploy any application regardless of the tech stack can be a sprint all in itself. So many questions to answer: What CI/CD pipeline do you use? Can't we just use the CLI? What about right-click-publish? Git Deploy? npm, yarn ? Docker, Kubernetes, Swarm, Containers...oh my!?!?! Yes or "it depends" is always the answer to these questions depending on the development shop you're working in. Docker, in version 1.17, introduced the concept of multi-stage builds which in short allows you to (in a single docker file) create images and utilize the output from one into the next to produce a final image and reduce the need for build scripts etc. See...

In my most recent Pluralsight course, I spent some time talking about using Swashbuckle to create documentation for ASP.NET Core WebAPI applications. Swashbuckle is the .NET Core implementation of the OpenAPI Specification aka Swagger, but there are many other open source tools too for other languages. The demo project built was a simple "traditional" ASP.NET Core API that generated a "Superhero Name" based on a FirstName and LastName passed to the GET method. The old API architecture The architecture would not surprise anyone who has seen an MVC structure for ASP.NET Web API projects, except the .NET Core portions. Controllers, Views, Startup.cs, etc., published to an Azure AppService running on IIS. If this were a node....

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. dotnet new The new command now is driven by a whole new template system. A number of new templates, including webapi, are available with the ability to install and create...

I use OSX as my primary development machine but still at time run to Visual Studio for work stuff, new features I'm testing etc. The most recent reason is Visual Studio '15 Preview and the new Docker features that are quite awesome. I didn't want to fire up the ThinkPad, connect it to the big monitor etc; so it was time to get Docker working on Parallels. Come to find out it was a few simple configurations. Check the "Enable nested virtualization" option under Hardware / CPU & Memory - Advanced Settings of your Windows 10 VM. Another setting I might suggest is setting the Memory somewhere between 4 - 8 GB of RAM or Docker may not start. Shared Drives...