Welcome to the Lounge

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.
}

Sam Hobbs wrote:

In many ways, Microsoft's technology is behind that of half a century ago and UWP is weighed down by that

jeffery c wrote:

If I post some code here and articles would people be interested in UWP?