Thorough. But completely missing anything async-based which is fundamental for scalability in IO scenarios like working with a db.
Thanks. But did you know that in .Net Core all the command methods have an Async conterpart (ExecuteNonQueryAsync, ExecuteReaderAsync, ExecuteScalarAsync)?
Yes... that is exactly what I mean. I feel that given it's availability your article should be demonstrating the async versions, and noting that non-async is available if you absolutely need it.
I usually try to include the least amount of concepts required to explain/demonstrate an idea, that's why Async isn't there.
You're right. async, await and Task<> really add a ton of code...
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.