@danpdc Sure that means a lot of "repeated" properties, but any IDE will fill those in with 1 or 2 keystrokes, and the compiler will keep you honest if the interface changes
@danpdc There may be logic that applies to "things with an EntityID", or things with "CreateTime and UpdateTime", or both. These constraints can be composed together using multiple inheritance and generic type constraints. Abs. class eliminates that composition
@badamczewski01 Big ORMs that abstract a Relational DB away into a Document DB are never a good idea IMO. If that's what you really need then use an actual Document Store DB. Don't try and shoehorn abstractions on top of one another until you get one.
@badamczewski01 I deal with this at work. "Why is it so slow" - because the ORM doesn't know how to use the database - "How did you make it so much faster?" - I used the database
I have never seen incompetence on this scale, impact and depth before.
For years I have adhered to a principle of curating the information I consume. Your mind is not as resilient as you think it is.
Elmo is now paying a heavy price for consuming garbage.
Paintโ.NET v5.0 is on .NET 7! Total conversion time was about 5 minutes. Had some compile errors because WinForms added some new nullable annotations. Also I got a (non-spam) phone call in the middle of it all.
@slace@droyad@chris_noring It is relatively easy using preprocessor directives and conditional ItemGroups in csproj files. Still harder than good first-class support for inline tests, but not nearly as hard as you might think.
@firstdrafthell I managed to implement inline tests using preprocessor directives and conditional PropertyGroups in the csproj files.
It was alright. First class support would be a lot nicer