Home/ Questions/Q 5932677
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T14:52:02+00:00

I have a very complex WPF application where the pages that I display and

  • 0

I have a very complex WPF application where the pages that I display and processed are in dlls. This works fine so far.

I set up a timer in the main page of the app that looks for communication coming in from an external source. When I get a communication (and I am being vague to not not add confusion) I parse it and if the message is “xyx” I need to start the XYL dll’s UI. I get the calling thread must be sta bacause many ui components require this.
I see the write ups on the web about having to call the Invoke() and that I can’t use a worker thread but rather a background thread.

Is my problem the System.Timers.Timer that I am using? Is that causing a worker thread? I am not sure where in my calls I need to start a thread to run this (or how to handle it).

Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    System.Timers.Timer runs on a worker thread and cannot access UI elements. See here and here for more information on that.

    It’s ok to use that kind of timer, you just need to get back to the UI (dispatcher) thread before you touch the UI pieces. You can do this by calling Dispatcher.Invoke or Dispatcher.BeginInvoke and passing in the delegate you want to run. That’ll get the new UI pieces onto your original UI thread. If you want them to run on their own UI thread (perhaps in a different window) then you need to set that up yourself.

    • 0