A collection of 82 posts
While never sold as an outright replacement for ASP.NET Core MVC, ASP.NET Core Minimal APIs are bound to have developers asking, “Which one should I use?” The answer depends on your use case, but in reality, you can use all...
The ASP.NET team built ASP.NET Core Minimal APIs to help developers build more concise and efficient web APIs. The approach has fewer features in favor of improved resource utilization and higher request throughput. One of the features to be “removed”...
The release of .NET 6 unleashed a wave of ASP.NET Core goodies on the development community. Some features received much attention, while some flew silently under the radar. One of the features I recently discovered was CSS isolation and JavaScript...
Have you ever needed the results of a method in an instance, but not have the required dependencies to instantiate the object? If you answered yes, let me start by saying you’re a weirdo, a good weirdo, but still a...
I’ve recently talked to folks from the #100devs boot camp, which got me thinking about the software development interviewing process. Not that I’m looking for a new job, but what questions would I expect to get during a technical interview...
I’ve recently spent a lot of time with my newest obsession, HTMX, and it’s seriously great. However, a challenge I face frequently is how to manage JavaScript dependencies in my ASP.NET Core applications. There’s NPM, Yarn, Gulp, Grunt, Webpack, Parcel,...
I was recently in an office hour with folks who had recently upgraded an ASP.NET Core MVC application to .NET 6. All UI interactions began failing with very odd behavior in the upgraded version: Request models were entering actions as...
The ASP.NET testing story has gotten easier with each new iteration, emphasizing dependency injection and inversion of control (IoC) containers contributing much of the plumbing for your web applications. Along with more accessible configuration options, we also see more opportunities...
.NET’s greatest strength is its long history of supporting developers through each industry paradigm shift, but just because there’s a new way of doing things doesn’t mean the established method goes away. It’s also a source of confusion and frustration...
Love it or hate it, The minimal templates in .NET 6 are here to stay. However, while some applaud minimal templates for their simplicity and clarity, some in the community find the change potentially confusing. I can see both sides...
