Currently working as a contractor, mostly on Node.js and Typescript, also React.
Also have a background in academia, I have a PhD in CS and worked as a researcher in AI.
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.
Currently working as a contractor, mostly on Node.js and Typescript, also React.
Also have a background in academia, I have a PhD in CS and worked as a researcher in AI.
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
asyncversions, and noting that non-asyncis 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,awaitandTask<>really add a ton of code...