Home > Articles > Web Development > ASP.NET

Silverlight Best Practices: Asynchronous Programming

Microsoft MVP for Silverlight Jeremy Likness covers asynchronous programming techniques. Learn how to call your web services in a way that prevents performance bottlenecks or blocking on the UI thread when processing complex results, understand the differences between the event-based and asynchronous programming model, and discover techniques for handling sequential asynchronous workflows in a way that keeps your code easy to read and maintain.
Like this article? We recommend

Silverlight provides a robust networking stack with the ability to load web pages, interface with web services, and parse RSS feeds out of the box. Unlike the desktop-based framework, the Silverlight client runtime does not allow synchronous operations and requires network-based operations to be asynchronous. While asynchronous and event-based programming models have been a part of the .NET Framework since the earliest versions, orchestrating sequential and parallel asynchronous workflows can be problematic, especially when trying to maintain code readability and maintainability.

Fortunately, several best practices can be utilized to simplify and extend asynchronous processes. This article will cover several of these approaches. The right approach depends on the target audience, development team and environment, and coding style. You will also learn how to call web services from Silverlight the correct way to control whether the response returns on the UI thread.

Asynchronous Events

Events are provided by the .NET framework to allow classes to provide notifications when something interesting happens. Events use delegates as templates. The following code snippet illustrates the default template for an event:

public delegate void SomethingHappenedEventHandler(object sender, EventArgs args);

The delegate can then be used to expose the event, like this:

public event SomethingHappenedEventHandler SomethingHappened;

An event can only be invoked by the class that owns the event. This is referred to as raising the event. The class that owns the event simply calls the event and passes the sender (usually the class itself) and the event arguments that are associated with the event, like this:

SomethingHappenedEventHandler(this, EventArgs.Empty);

The class that raises this event can be referred to as the publisher. To receive notifications for an event, or to subscribe to the event, the subscriber simply attaches a delegate for the class to call when the event is raised (or published). For example, the following subscriber class creates an instance of the publisher and writes a message to the debugger whenever the “something happens” event is published:

public class Subscriber
    private readonly Publisher _publisher = new Publisher();

    public Subscriber()
        _publisher.SomethingHappened += 

    void Publisher_SomethingHappened(object sender, 
        EventArgs args)
        Debug.WriteLine("Something happened!");

Events are asynchronous because they allow the interested class to register for the event then perform other tasks until something interesting happens. When the event is published, the subscriber is notified and can then respond to the event. The event model is the default model used to invoke web services in Silverlight (the proxy that is generated when you add a service references exposes events and event arguments). Consider a web service with the following signature:

[ServiceContract(Namespace = 
public interface IMyServices
    int Add(int x, int y);

The following code is required to call the service. Note that the call is asynchronous because the code does not “wait” for the result. Instead, it registers for the event of receiving the result then begins the request. At this point, the main thread of code has stopped executing. This is because the request must be sent over to the network, received by the service, processed, and then returned to the Silverlight client. Once the request returns, the service client processes the result and raises the event.

public void CallService()
    var client = new HostServices.MyServicesClient();
    client.AddCompleted += client_AddCompleted;

void client_AddCompleted(object sender, HostServices.AddCompletedEventArgs e)

All services by default generate the complementary methods that end with Async to begin the request and raise the Completed event when the request is finished.

One immediate issue with this approach is that the model is not easy to test. The client must be created, and all of the services set up appropriately in the environment. Creating a “pretend” service requires exposing an event and processing the result. The result is highly coupled code. The subscription to the event creates a reference that can result in memory issues later because unregistered events may not be garbage-collected. The first step to fix these challenges is to decouple the code. The .NET Framework provides the perfect class to accomplish this: the Action class.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020