Shawn Wildermuth has been tinkering with computers and software since he got a Vic-20 back in the early ‘80s.
As a Microsoft MVP since 2003, he’s also involved with Microsoft as an ASP.NET Insider and ClientDev Insider. You may have taken one of his more than twenty courses on Pluralsight
He’s authored eight books and innumerable articles on software development. You can also see him at one of the local and international conferences he’s spoken at including TechEd, Oredev, SDC, NDC, VSLive, DevIntersection, MIX, Devteach, DevConnections and Dev Reach.
He is one of the Wilder Minds. You can reach him at his blog. He’s also making his first, feature-length, documentary about software developers today called “Hello World: The Film”. You can see more about it here.
I recently released a two-part course on C# 8. The first part is for beginning programmers. The second part is for intermediate to advanced programmers.
This post is the first in a series that focuses on the new features in C# 8.
I recently had Mads Torgenson on my Podcast. Mads is the lead designer of C#. I asked him what the most important new feature of C# is, and he replied (somewhat to my surprise) Nullable Types.
Every one of us has crashed and burned on the dreaded “object reference” exception. Null Reference types are designed to avoid these by expressing which objects might be null and having the editor issue a warning if you create an instance that might be null and try to dereference it.
Microsoft’s Sweeky Satpathy. Sweeky is a Senior Software Engineer in MOBCat the Customer Engagement Team, which is part of DevDiv product engineering team responsible for all of Microsoft’s developer focused products and services and represents the voice of the developer to the rest of Microsoft. She works closely with the Xamarin team.
In a previous blog post I discussed the problem of being in your ViewModel yet having to display a dialog to the user. You can’t interact with the page from the ViewModel, but you don’t want the logic of your program in the code-behind.
In that previous article, I demonstrated solving that problem using an event. In this blog post, Rodrigo Juarez and I will demonstrate three alternatives:
Using the Messaging System
Using Events (though here we’ll show a somewhat different approach)
Using dependency/service injection
There are significant problems with the first two; the most important of which is that they are difficult or impossible to write unit tests for. The third approach, however, is clean, efficient and very testable using a Mock service.