Options
Asynchrony in C# 5 Interactive Tutorial, updated for Framework 4.5 RTM
Some feedback on this downloadable tutorial:
I guess this is your problem and not part of C# 5 (but I haven't checked): If every await present has brackets around the expression, it decides "CS0103 The name 'await' does not exist in the current context" for all awaits. So your "await and exceptions" and "await in a loop" don't compile "out of the box".
Your sample png URL downloads need to have .../images/... inserted to work.
The downloaded string using WebClient is different to what is downloaded for HttpClient (so the total characters downloaded is different). I haven't determined what the difference is (I'm sure I can copy'n'paste the raw HTML into WinMerge if I really cared), but it's not CrLf differences.
After those issues, I've seen nothing else significant (but I haven't downloaded the suggested NuGet packages yet). (I call leaving B at 6000 instead of 2000 in "Task.WhenAny - double await" insignificant.)
I guess this is your problem and not part of C# 5 (but I haven't checked): If every await present has brackets around the expression, it decides "CS0103 The name 'await' does not exist in the current context" for all awaits. So your "await and exceptions" and "await in a loop" don't compile "out of the box".
Your sample png URL downloads need to have .../images/... inserted to work.
The downloaded string using WebClient is different to what is downloaded for HttpClient (so the total characters downloaded is different). I haven't determined what the difference is (I'm sure I can copy'n'paste the raw HTML into WinMerge if I really cared), but it's not CrLf differences.
After those issues, I've seen nothing else significant (but I haven't downloaded the suggested NuGet packages yet). (I call leaving B at 6000 instead of 2000 in "Task.WhenAny - double await" insignificant.)
Comments
await (brackets)issue, and I've now confirmed it seems to only affect C# Statement(s) queries, not C# Programs nor using the full VS2015 IDE, I guess it is a part of your logic to determine if the whole routine should be seen as async or not.But testing this did cause me to find a VB.NET bug I've reported.
http://www.linqpad.net/download.aspx#beta
Let me know how you get along.