The await keyword is a new keyword in C# 5.0 which, in tandem with async keyword, allows us to easily author methods which execute asynchronously in regards to the calling code. In previous posts I’ve shown certain issues you should look out for when using these keyword. In this post we’ll look at another issue with the await keyword – how to access the AggregateException. await Only Throws One Exception As we saw in a previous post, await (unlike Task.Wait()) does not wrap a thrown exception in an AggregateException and instead just re-throws the exception thrown within...
The await keyword is a new keyword in C# 5.0 which, in tandem with async keyword, allows us to easily author methods which execute asynchronously in regards to the calling code. In a previous post I’ve shown a certain issue you should look out for when using the async keyword. In this post we’ll check a similar issue with the await keyword.
The await Trap
Let’s remember our test code from the previous post:
public void Process(string s)
if (s == null) throw new ArgumentNullException("s");
Windows Workflow Foundation (WF) is a core .NET technology for authoring long-running, scalable & integrated business processes. The WF designer that ships with VS2012 is the main tool of choice for declaratively creating workflows in .NET 4.5, however, unfortunately, it has an issue with high Dots-Per-Pixel (DPI) settings.
Introducing the Windows DPI Settings
As computer monitors arrive with an ever growing resolution on smaller and smaller screens, you might have noticed that the text and icons you’re viewing in Windows are getting small, sometimes too small to be readable properly.
That’s exactly why Windows has a DPI Scale setting (In “Display” under...