Digests » 213
You guys are amazing 😍 I got a great feedback on the paid version of the digest and a few new subscribers! It helps me to keep producing better content and make this business more sustainable without selling your attention to advertisers. Also, a few of you asked me for a sample of the paid newsletters so check it out.
If you like it, please 💥subscribe💥! For just $5/month; which is less than you'd pay for a "funny" humping dalmatin smartphone cable; you will get a premium content into your inbox every Monday. It goes great with your morning coffee ☕️.
Not coming from a background in computer science, the inner workings of a computer have always been somewhat of a mystery to me. This is something I’ve always meant to remedy but never quite gotten around to. When I transitioned from C++ to C# my main thought surrounding memory management was “well thank god I don’t have to think about that anymore”. However, in the last few weeks I have been really drilling down into the inner workings of the language (a big thank you to Ian Griffiths for his book Programming C# 5.0).
.NET Core 2.1 is the latest release of the general-purpose development platform maintained by Microsoft and the .NET open source community. .NET Core is cross-platform and open source and consists of a .NET runtime, a set of reusable framework libraries, a set of SDK tools, and language compilers. Amongst many great features, this new release focuses on performance and brings us the System.Memory library that’s available right out of the box and is also available as a standalone package on NuGet.
Have you ever wondered what exactly is in a nuget to see if it’s right for you? You read the description, you like the name, but, if you’re like me, you probably ended up in GitHub reading the source code to decide if you want to use the library.
Every now and then we like to take a memory dump of this application from our production environment. We have done this enough times that we have automated the most common diagnostics steps we take and bundled them into a little tool¹ called ADA (Automated Dump Analysis). If you are interested you can find the tool here and all the code talked about in this article here.
Dynamic binding in C# opens some possibilities which would not be available in a strictly strong typed language. This tutorial explores how C# supports dynamic binding.