The problem Whilst I have mostly got the hang of async/await, I still find unexplored corners of the subject that catch me out. I came across one the other day that was (in retrospect) so obvious that I’m surprised it never caught me out until then. This blog post is an attempt to explain the problem and solution, so that when I want to remember the hows and whys in a few months, I will have something to read! As my regular reader will know, I am not under any illusions that anyone else reads my blog, nor that anyone else find it useful. I use it as a place to make notes of things that I’m likely to want to find again. If it helps anyone else, well that’s just a bonus! The actual background to the use case is irrelevant, so I’ll illustrate with a trivial example. Suppose…
Dot Net What Not Posts
A few examples of my rather poor experience with Copilot
Why my uploaded images weren’t being displayed in my Blazor app, and how I got around the problem, learning something new along the way.
Having struggled with EF Core adding shadow properties for navigation relationships, I finally found out what it’s doing and (more importantly) how to fix it.
The Blazor web app template introduced in .NET8 has some excellent features, but also has some subtle gotchas that can cause performance issues if you don’t handle them.
This post explains a utility class I wrote that will keep data access to a minimum when dealing with both server and client rendering, as well as caching data between navigations around the client code.
An updated version of my old message broker that allows MVVM-style messaging to be done between Blazor components.
Unlike the previous version, this one is naturally async and thread-safe
I wanted to speed up the performance of a Telerik Blazor grid. This post documents an extension method I wrote to enable this using EF Core. This was at least as fast (if not faster) than the previous method i wrote based on Dapper, and has some significant extra features
Last month, I explained how we had achieved a significant performance improvement by using Dapper to pull the data from the database, rather than using EF Core.
Whilst showing this to a colleague, he reminded me that EF Core has a FromSqlRaw method that does pretty much the same thing. Assuming that EF Core would be slower than Dapper, I didn’t give it much thought at the time. However, being a compulsive tinkerer, I decided to take a closer look.
This post explains my findings, and what I did with them
Due to some performance issues, I decided to try using Dapper with the Telerik grid for Blazor. This post documents the (excellent) results, and shows a useful extension method that makes this very simple.
Having upgraded an ASP.NET Core project from .NET7 to .NET8, I got an error when trying to publish it. This blog post is my note to remind me how to fix it
Leave a Comment