Stephen Cleary
@astevecleary.bsky.social
Christian, husband, father, developer. MS MVP. O'Reilly author. Armchair theologian. Violinist. Avid reader.
No problem; it happens. Thanks!
November 14, 2025 at 2:08 AM
No problem; it happens. Thanks!
Sorry for the confusion. When I wrote that post, I had not used EF for years, but I remembered it was a pretty big thing that they had not used CA(f). I wasn't aware they added CA(f) later. The post has been corrected.
October 19, 2025 at 11:00 AM
Sorry for the confusion. When I wrote that post, I had not used EF for years, but I remembered it was a pretty big thing that they had not used CA(f). I wasn't aware they added CA(f) later. The post has been corrected.
IMO usually in these cases, I would say that an event isn't the correct implementation. This is usually because events are being (mis)used to implement the strategy pattern. If it's truly a notification, then either 1) top-level exceptions are correct, or 2) save the task and await it later.
October 19, 2025 at 1:46 AM
IMO usually in these cases, I would say that an event isn't the correct implementation. This is usually because events are being (mis)used to implement the strategy pattern. If it's truly a notification, then either 1) top-level exceptions are correct, or 2) save the task and await it later.