Why does Radzen Studio create synchronous calls instead of asyncronous?

Hello,

we were wondering why the DataService created by Blazor Studio when importing a datasource for CRUD is using syncronous calls to the database instead of the asynchronous ones, for example when creating Records, the generated code uses SaveChanges() and not SaveChangesAsync().

I failed to find the reasoning behind that, and maybe there is an explanation for it or some side effects i am not aware of. Can someone elaborate on that?

There isn't any particular reason, however since these methods are executed inside of async Task there will be no difference in my opinion. Here is also interesting read on the same topic:
https://medium.com/@iamprovidence/addasync-in-ef-is-pure-evil-d31231d8f04e

1 Like