Some call APIs but the vast majority are just mapping calls. Changing one
object into another.
Davy
On Tue, 26 Mar 2019, 21:51 Greg Keogh, wrote:
>
> This is pretty typical for the entire project.
>> var legalEntity = await CreateLegalEntityObjectAsync(...);
>> var billingAccount =
> This is pretty typical for the entire project.
> var legalEntity = await CreateLegalEntityObjectAsync(...);
> var billingAccount = await CreateBillingAccountObjectAsync(...);
>
But what's inside all the awaited methods? Are they actually doing anything
asynchronously (web service calls,
Yes David, there are whole chains of method calls, all awaiting for
something to complete, the only part that is not async is the database call!
*... .. / --- -.-. / .-.. . --. . .-. . / ... -.-. .. ... / -. .. --
.. ..- -- / . .-. ..- -.. .. - .. --- -. .. ... / .- -... . ... .-.-.-*
Presumably inside these methods are other calls to additional async
methods?
This sounds like an example of how "viral" the async/await stuff can be, in
that once you call an async method at the lowest level, everything further
up ends up needing to become "async/awaited" too.
David
On Tue, 26
Hi Greg,
This is pretty typical for the entire project.
var legalEntity = await CreateLegalEntityObjectAsync(...);
var billingAccount = await CreateBillingAccountObjectAsync(...);
var billingAccountUid = billingAccount.UserName;
var billingAccountTaxServiceAddressPcode =
*forking* hell!
regards,
Preet, in Auckland NZ
On Tue, 26 Mar 2019 at 22:52, Greg Keogh wrote:
>
> I've started a new post, and one of the applications here uses Async Await
>> for nearly every method call, even for simple calls that just create an
>> object and return it.
>>
>
> How on
> I've started a new post, and one of the applications here uses Async Await
> for nearly every method call, even for simple calls that just create an
> object and return it.
>
How on earth is that sort of thing coded? How are intrinsically synchronous
methods forcibly turned into async ones? Is
