Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 954523
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T00:13:43+00:00 2026-05-16T00:13:43+00:00

I’m working on this Silverlight 3.0 Project that is completely filled with Async Calls

  • 0

I’m working on this Silverlight 3.0 Project that is completely filled with Async Calls to a Web Service. At the Main Page it fetches some needed data in order for the application to work correctly using 3 Async Calls. Right now the application does not disable any controls while executing those calls meaning a user can interact with it without that needed data. I need to disable the whole grid and only after all 3 Async calls are finished then and only then enable the grid.

What’s the best practice for doing this.

These are my calls:

client.GetAllAsync();
client.GetAllCompleted += new EventHandler<GetAllCompletedEventArgs>(client_GetAllCompleted);

client.GetActualAsync();
client.GetActualCompleted += new EventHandler<GetActualCompletedEventArgs>(client_GetActualCompleted);

client.GetSomeAsync();
client.GetSomeCompleted += new EventHandler<GetSomeCompletedEventArgs>(client_GetSomeCompleted);
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T00:13:44+00:00Added an answer on May 16, 2026 at 12:13 am

    Seems lot a lot of work just to queue some user interactivity.

    I typically provide an application-wide interface:

    public interface IAppGlobalState 
    {
       void BeginAsync(); 
       void EndAsync(); 
    }
    

    In the implementation, I’ll do this:

    public partial class MainShell : UserControl, IAppGlobalState 
    {
       private int _queue; 
       private object _mutex = new Object();
    
       public void BeginASync()
       {
          Monitor.Enter(_mutex);
          if (_queue++ == 0)
          {
             VisualStateManager.GoToState(this, "BusyState", true);
          }
          Monitor.Exit(_mutex);
       }
    
       public void EndAsync()
       {
          Monitor.Enter(_mutex);
          if (--_queue == 0)
          {
             VisualStateManager.GoToState(this, "IdleState", true); 
          }
          Monitor.Exit(_mutex);
       }
    }
    

    Of course if you have heavy multi-threading then you’ll use Interlocked on those but most of the time you’ll be invoking it from the same thread. Then, you simply do:

    GlobalState.BeginAsync();
    client.FirstAsyncCall();
    
    GlobalState.BeginAsync();
    client.FirstAsyncCall();
    

    And then on the return, just:

    GlobalState.EndAsync();
    

    If you have nested calls, no problem, this method unwinds them.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.