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

  • Home
  • SEARCH
  • 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 6971549
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T16:51:15+00:00 2026-05-27T16:51:15+00:00

I always thought I could use SynchronizationContext to marshal a call to another thread.

  • 0

I always thought I could use SynchronizationContext to marshal a call to another thread. Apparently I was wrong as SyncCtx.Send() doesn’t do anything but invoking the given delegate (stays on the same thread). Do I really need to derive from SynchronizationContext and do work on the thread context? I feel like missing something.

What I want to achive: Imagine a little API for executing commands within an app. You can also execute a command on a background thread, as you can assign a delegate to run when the command has finished execution. This “Call-me-when-done”-Delegate gets one single paramter (State) containing success/failure flag, optional exception information, etc. I want to call this delegate on the original calling thread so that devs using the lib do not need to handle invoke required etc. I would just like to take this away and let them do simple non-thread-aware programming. WindowsFormsSynchronizationContext doesn’t seem to help either if you don’t give it some control as a target.

Thanks for any help!

  • 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-27T16:51:16+00:00Added an answer on May 27, 2026 at 4:51 pm

    When you are in winforms and you use the synchronizationcontext the call will be marshalled to the GUI thread.

    for your specific case I guess something like this should work, probably it will be a good idea to create a class that represents a Command

    public class CommandManager
    {
        private readonly SynchronizationContex _synchronizationContex;
    
        public CommandManager(SynchronizationContext synchronizationContex)
        {
            _synchronizationContex = synchronizationContex;
        }
    
        public void ExecuteAsync(Func<State> action, Action<State> callback)
        {
            ThreadPool.QueueUserWorkItem(o => {
                                                 state = action();
                                                 _synchronizationContex.Send(oo => callback(state));
                                              });
        } 
    }
    

    you’d create like this (in the GUI thread, so for example in your main form)

    var commandManager = new CommandManager(SynchronizationContext.Current);
    

    you’d use it like this:

    commandManager.ExecuteAsync(() => new State() { Success = true }, 
                                 c => MessageBox.Show("success in the GUI thread"));
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I always thought an SQL compiler would break but apparently nesing can nearly be
I always thought that implicit constructor in C++ could only be a constructor with
I have an odd question that I have always thought about, but could never
JCombobox in Java 7 has been updated to use generics - I always thought
I always thought they were about the same thing but someone pointed me out
I always thought operator is determined if the given variable is of the given
I always thought that if you didn't implement a heartbeat, there was no way
I always thought that parentheses improved readability, but in my textbook there is a
I always thought that when you dropped a control onto an .aspx page that
I always thought that internal class has access to all data in its external

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.