A few months back we asked the Octopus community if they could spare a few minutes and brain-cycles to provide some feedback on the first-draft of our Kubernetes plans. And you certainly delivered. So first, thank-you! We sincerely appreciate everyone who shared their thoughts. The product will certainly benefit from it.
This is pretty interesting as I’ve always really loved Octopus but felt it a bit out of place for dealing with container images. They are hitting the nail right on the head with point #3 on something similar that I’ve done.
Customers are even simulating these by including dummy packages (e.g. NuGet or Zip) in their deployment process to represent their container images, since these would be captured in the release. This is very clever, but also made us sad. It shouldn’t require that level of ingenuity.
In this post I describe how and why I created a .NET Core global tool to easily convert configuration stored in web.config files to the JSON format more commonly used for configuration in ASP.NET Core.
Really helpful post if you’re migrating from an web.config to asp.net core and want to transition to json config.
I was recently speaking with someone regarding the .NET GC and memory and immediately thought of this talk. Highly recommend checking it out if you are unfamiliar with how the GC works and when memory is allocated in .NET.
The .NET Garbage Collector (GC) is really cool. It helps providing our applications with virtually unlimited memory, so we can focus on writing code instead of manually freeing up memory. But how does .NET manage that memory? What are hidden allocations? Are strings evil? It still matters to understand when and where memory is allocated.
In this talk, we go over the base concepts of .NET memory management and explore how .NET helps us and how we can help .NET – making our apps better. Expect profiling, Intermediate Language (IL), and using ClrMD to mimic some inspections dotMemory provides.