Here’s a workaround I found that works for all cases (including suspended dispatchers). It’s not my code and I’m still working to fully understand it, but it does work. It can be called using: customerList = AsyncHelpers.RunSync<List<Customer>>(() => GetCustomers()); Code is from here public static class AsyncHelpers { /// <summary> /// Execute’s an async Task<T> … Read more
Async arrow functions look like this: const foo = async () => { // do something } Async arrow functions look like this for a single argument passed to it: const foo = async evt => { // do something with evt } Async arrow functions look like this for multiple arguments passed to it: … Read more
Asynchronous programming does “grow” through the code base. It has been compared to a zombie virus. The best solution is to allow it to grow, but sometimes that’s not possible. I have written a few types in my Nito.AsyncEx library for dealing with a partially-asynchronous code base. There’s no solution that works in every situation, … Read more
When using async and await the compiler generates a state machine in the background. Here’s an example on which I hope I can explain some of the high-level details that are going on: public async Task MyMethodAsync() { Task<int> longRunningTask = LongRunningOperationAsync(); // independent work which doesn’t need the result of LongRunningOperationAsync can be done … Read more
Sure the code does work, but I’m pretty sure it doesn’t do what you expect it to do. It just fires off multiple asynchronous calls, but the printFiles function does immediately return after that. Reading in sequence If you want to read the files in sequence, you cannot use forEach indeed. Just use a modern … Read more