Digests » 204
Big thank you to everyone who completed the short survey last week. I really appreciate your feedback and want to make C# Digest better – if you haven't done it yet, please take a few minutes and fill it out for me.
CNN describes our app well: “Blind is an anonymous app for tech workers to discuss, debate and gossip about compensation, corporate policies, workplace harassment, and more.” Blind, which was once banned by Uber, is now used by 7,000+ Uber engineers, designers, and PMs. If you work in tech, your coworkers are on Blind. Download the app and join your coworkers today at TeamBlind.com!
“Why would you ever want to use ASP.NET, are you still stuck in the 90’s?”, these are the exact words uttered by an old coworker of mine when I brought up the idea of considering using ASP.NET for a project we were about to start a couple years ago. I agreed with him for the most part at the time. Microsoft had developed a great language, great web framework and great tooling around it yet people were still not too happy about it.
Recently, the topic of using someObject is null over someObject == null has been coming up, and I'd like to give my two cents on the issue - in particular, I'd like to make the case for using is null in every case where you would previously use == null.
It really can't be overstated how useful a resilience framework for .NET Core like Polly is.
Blazor is an exciting new web framework from the ASP.NET team that uses Razor, WebAssembly, and Mono to enable the use of .NET on the client. There’s been a lot of excitement about the possibilities this presents, but there’s also been just as much confusion about how these various parts fit together. In this post I’ll attempt to clarify things and show you exactly what each of these technologies do and how they work together to enable .NET in your browser.
A tiny, cross-platform, module based, MIT-licensed web server for .NET Framework and .NET Core