a developer's journey with asp.net core and the web
I’m a gamer. Video games are what initially interested me about computers. DOS prompts, autoexec.bat, config.sys, and a batch loader to reconfigure the system depending on which game I wanted to play was where I first learned how to configure things. Growing older, however, I find that I don’t have the time for my hobby and I fall increasingly behind on my gaming backlog. Exploring the internet I’ve compiled a way that works for clearing my gaming backlog.
Recently I was going through the motions upgrading an ASP.NET Core 2.0 website to 2.2. Overall the process was fairly straightforward, minus some gotchas. We were attempting to switch the website from targeting the full framework (net47) to target netcoreapp2.2 but that caused a cascade of problems. One such problem was WCF. Today we’ll discuss using WCF with .NET Core and some of the gotchas you may run into.
User experience (UX) is a fine art and many developers fail at it. Years ago I watched a basic UX course on PluralSight by Billy Hollis. Since that time I have tried to focus on UX. One thing I’ve learned over the years is how awful modal confirmations are for delete operations. Today we’ll look at another way to approach delete actions by introducing a delayed cancelable action button in React.