#251 – March 24, 2019
Optimize and transform images with ImageKit.io - a complete image management solution
Want to optimize images for better page load time, SEO and UX? ImageKit, with its global delivery network, automatic compression, best format selection with WebP support, URL-based resizing, smart cropping and overlays, makes managing & optimizing images easier. Works with AWS S3, Magento, Shopify, Wordpress, and any other web server. Use it for free up to 20GB output bandwidth per month. Get custom domain names and additional features on the premium plan.
Immutable Records could be added in C# 8
Since Microsoft rebuilt the C# compiler into what is now the Roslyn compiler, the language teams’ feature implementation speed has been phenomenal, they are cranking features out in record time. Pro C# 7: With .NET and .NET Core Microsoft is committed to continuously update the C# language. They have even given us incremental updates of features that were not yet ready for the major versions release date and subsequently added it in minor language updates, such as C# 7.1, 7.2 and 7.3.
Back in 2012, Microsoft released C# 5 with a handful of new features, one being ‘async/await’. At the company I work for, we bypassed this new feature completely, and judging by what I’ve read online, we’re not alone! However, I’m finding that more and more projects I see on GitHub are using it, and there’s generally a lot of buzz around it, and it’s widely regarded as one of the best recent features in C#.
Why is string.GetHashCode() different each time I run my program in .NET Core?
In this post I describe a characteristic about GetHashCode() that was new to me until I was bitten by it recently - that calling GetHashCode() on a string gives a different value each time you run the program in .NET Core!
The following are few tips and tricks for working with async in C#. This is as much a reference for myself as anyone else, but I figured it would probably useful for others as well.