So far, we have only observed problems related to multithreaded access to the UI controls. By default, the C# await statement will use the current synchronization and execution contexts and post the continuation code to the appropriate environment. Is there any use for the ConfigureAwait method? Why should we ever try to change the default behavior? To answer this question, consider the following application. This time we will review the whole code including the one that assembles the application:
private static Label _label;
[STAThread]
static void Main(string[] args)
{
var app = new Application();
var win = new Window();
var panel = new StackPanel();
var button = new Button();
_label = new Label();
_label.FontSize = 32;
_label.Height = 200;
button.Height = 100;
button.FontSize = 32;
button.Content = "Start asynchronous operations";
button.Click += Click;
panel.Children.Add(_label);
panel.Children.Add(button);
win.Content = panel;
app.Run...