Hi Greg,
This is pretty typical for the entire project.
var legalEntity = await CreateLegalEntityObjectAsync(...);
var billingAccount = await CreateBillingAccountObjectAsync(...);
var billingAccountUid = billingAccount.UserName;
var billingAccountTaxServiceAddressPcode =
billingAccount.InternalView.TaxServiceAddressPcode;
var primaryGroup = await CreatePrimaryGroupObjectAsync(....);
Davy
*... .. / .... --- -.-. / .-.. . --. . .-. . / ... -.-. .. ... / -. .. --
.. ..- -- / . .-. ..- -.. .. - .. --- -. .. ... / .... .- -... . ... .-.-.-*
On Tue, Mar 26, 2019 at 11:10 AM Preet Sangha <preetsan...@gmail.com> wrote:
> *forking* hell!
>
> regards,
> Preet, in Auckland NZ
>
>
>
> On Tue, 26 Mar 2019 at 22:52, Greg Keogh <gfke...@gmail.com> 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 earth is that sort of thing coded? How are intrinsically
>> synchronous methods forcibly turned into async ones? Is it like this?...
>> (I'm just guessing)
>>
>> var foo = await Task.Run(() => return new Foo());
>>
>> *Greg K*
>>
>>>
