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,
!
*... .. / --- -.-. / .-.. . --. . .-. . / ... -.-. .. ... / -. .. --
.. ..- -- / . .-. ..- -.. .. - .. --- -. .. ... / .- -... . ... .-.-.-*
On Tue, Mar 26, 2019 at 2:34 PM David Gardiner
wrote:
> 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 le
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
:10 AM Preet Sangha wrote:
> *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 met
*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 ret
> 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 int
Hello all,
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.
Are there any pitfalls for using this many await methods in an application?
Davy.
*... .. / --- -.-. / .-.. . --. . .-. . / ... -.-. .. ... / -. .. --
.. ..- -- / . .-. ..- -.. .. - .. --- -. .. ... / .- -... . ... .-.-.-*
of us who are
abstraction wonks.
Thanks.
On Wed, Oct 24, 2012 at 12:25 PM, David Kean david.k...@microsoft.comwrote:
We just released an updated async package that enables async/await on
.NET Framework 4, Silverlight 4 5, Phone 7.5 and portable library
combinations:
http://blogs.msdn.com/b
package that enables async/await on
.NET Framework 4, Silverlight 4 5, Phone 7.5 and portable library
combinations:
http://blogs.msdn.com/b/bclteam/archive/2012/10/22/using-async-await-without-net-framework-4-5.aspx
** **
Tell me what you think.
--
regards,
Preet, Overlooking
We just released an updated async package that enables async/await on .NET
Framework 4, Silverlight 4 5, Phone 7.5 and portable library combinations:
http://blogs.msdn.com/b/bclteam/archive/2012/10/22/using-async-await-without-net-framework-4-5.aspx
Tell me what you think.
11 matches
Mail list logo
