I think I somewhat have it sorted. But I find it is a deficiency of CommunityToolkit.Mvvm the ObservableObject. And I do not really want to get into the constroversy over DTO to the database and what not. That's not what this is. We're talking about hydrating models, from the ground up.
OO implements the INPC pattern among other things, allows for nice setting of properties, which I think is a huge plus, does not change a prop value unless it has to. Which in ORM and NH or EF terms, also means not upserting when it does not see a change.
Anyway the events are not implemented virtual. I tried new virtual in my classes, to no avail since apparently somehow the first declaration of the event is winning.
So I may either look at an Mvvm PR if possible, or just implementing my own virtual version.
Of course, if I can disable lazy loading, which I do not necessarily need or want, then perhaps that is a non issue, yes?
Best...
Michaael W. Powell