Welcome to the Lounge

jeffery c wrote:

Those 70-80's languages are only used in nasa mainframes

jeffery c wrote:

most users barely know where the power button is on their computer

Sam Hobbs wrote:

I was actually in her office in the basement of the Pentagon once.

jeffery c wrote:

using virtual box with the windows phone image

Afzaal Ahmad Zeeshan wrote:

The thing is, that entire of the Windows Runtime was developed on top of async/await pattern

Marc Clifton wrote:

bothering to even learn more about it.

1. You don't use async/await at all. You perform all the operations synchronously.
2. You write every function call, with an await operator. That way, most of the errors (such as Illegal operation, Invalid state) etc would go away.

1. Illegal state
2. Invalid operation
3. Infinite loop

Afzaal Ahmad Zeeshan wrote:

I think, in the next update Microsoft should work on these things, to make sure asynchrony is managed by OS itself and even being a feature of language, stays as a pain of the kernel only.

public class Whatever
{
    public async Task<int> ReturnTwoSynchronously() => 2; //Synchronous currently, access to await if you want
    public int ReturnTwoSynchronously2() => 2; //Make the above represented by this standard pattern. As long as await is not used to create asynchronous behavior it will run synchronously.
}