Carlos Mendible

You start developing an ASP.NET Core application to run it in Kubernetes and suddenly you find yourself creating a docker file, building an image, pushing the image to a registry, creating both a deployment and a service definition for Kubernetes and you wonder if there is a tool out there to help you streamline the whole process.

For my recent talk at .NET Conf Madrid I managed to install Elastic Search, Fluentd and Kibana (EFK) as a logging solution for the AKS cluster I used in my demos. The fact is that such deployment was possible thanks to Tim Park and his post Logging with Fluentd, ElasticSearch, and Kibana (EFK) on Kubernetes on Azure where I learned that to effectively deploy EFK on AKS I would have to tweak the resource definitions found in the Kubernetes project.

On April I wrote a post about Using Docker Multi Stage Builds to build an ASP.NET Core Echo Server and these days while preparing a talk, on CI/CD and kubernetes, I started to play with the simple sample I wrote back then. Soon enough I noticed that with each docker build command I issued the dependencies for the echoserver were always restored, even if no changes were made to the project file (csproj).

Last week I read this tweets from Maxime Rouiller (@MaximRouiller): Are you an MVP with a #dotnetcore #nuget package? Are you looking for an easy blog post? I have something for you. — Maxime Rouiller (@MaximRouiller) August 22, 2018 Actually, you're already using it. https://t.co/N5IaY6TGqQ That project is freaking cool. We need more package author to use it.

So what is faster: looping through a List<> with for or with foreach? Today I’ll show you how to use BenchmarkDotNet with .Net Core to answer that question. Let’s start: Create a folder for your new project # Open a command prompt an run:

You have to choose between using string.compare or == to compare strings. How would you know which method performs faster? Today I’ll show you how to use BenchmarkDotNet with .Net Core to answer that question. Let’s start: Create a folder for your new project # Open a command prompt an run: