Async invocation pattern

I talked to my colleague Alex Thissen recently about the changes in asynchronous invocation of ASP.NET 2.0 webservices. On the web there are a multitude of examples about the old way, but not so many on the new way. But after figuring out what the new way was, I started asking myself why they changed it. Probably for the benefit of readability and ease of use. But still, it’s not the first time I questioned why and how.

After discussing this with Alex, he wrote a weblog post on the ASP.NET 2.0 async invocation pattern and showed the old and new way of doing things. In this weblog post I wanted to show the subtle difference between the VB.NET and C# versions.

In Visual Basic.NET 2.0

Sub Main()

  Dim proxy As New HelloWorldService.Service()

  AddHandler proxy.HelloWorldCompleted, AddressOf HelloWorldCompleted

  proxy.HelloWorldAsync()

 

  Console.WriteLine(“Press any key to exit…”)

  Console.ReadKey()

End Sub

 

Public Sub HelloWorldCompleted(ByVal sender As Object, ByVal args As HelloWorldService.HelloWorldCompletedEventArgs)

  Console.WriteLine(args.Result)

End Sub

In C# 2.0

static void Main(string[] args)

{

  HelloWorldService.Service proxy = new HelloWorldService.Service();

  proxy.HelloWorldCompleted += new HelloWorldService.HelloWorldCompletedEventHandler(proxy_HelloWorldCompleted);

  proxy.HelloWorldAsync();

 

  Console.WriteLine(“Press any key to continue…”);

  Console.ReadKey();

}

 

static void proxy_HelloWorldCompleted(object sender, HelloWorldService.HelloWorldCompletedEventArgs e)

{

  Console.WriteLine(e.Result);

}

You may also like...

Click on a tab to select how you'd like to leave your comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.