or subscribe with
Join 19,000+ readers for one email each week.
Digests » 139
Are you passionate about presentation? Improvement Interactive is searching for a Software Trainer who is also knowledgeable about Git to travel to several destinations per month to conduct in-person seminars. Send your resume to [email protected]
this week's favorite
Hey, have you heard of the new Azure services: Elasticville, StorageWart and API Gatesian? Of course not, I just made those up.
Image processing, and in particular image resizing, is a common requirement for web applications. As such, I wanted to paint a panorama of the options that exist for .NET Core to process images. For each option, I’ll give a code sample for image resizing, and I’ll outline interesting features. I’ll conclude with a comparison of the performance of the libraries, in terms of speed, size, and quality of the output.
In this post, we will establish a performance comparison among several freely distributable embedded database technologies for the .NET crowd. Your real-life mileage may vary (depending on your exact usage scenario), so make sure to run your own (more specific) benchmarks as required. Also, keep in mind that performance (while important) is only one of the many aspects to consider when choosing an embedded database technology (together with ease of development and enhancement, availability and quality of tooling, ease of maintenance, licensing and distribution, …).
In this blog entry, we would like to discuss some significant changes that were made in the .NET 4.6.x garbage collector (GC). We encourage you to get the latest version, 4.6.2. Our main GC developer, Maoni Stephens wrote up a description of the enhancements that were delivered with the 4.6.2 framework. These changes were made in order to improve performance of the framework and to allow the garbage collector to operator more efficiently.
Delegates are a fundamental part of the .NET runtime and whilst you rarely create them directly, they are there under-the-hood every time you use a lambda in LINQ (=>) or a Func<T>/Action<T> to make your code more functional. But how to they actually work and what’s going in the CLR when you use them?