Note that there are some explanatory texts on larger screens.

plurals
  1. USMarko
    primarykey
    data
    text
    plurals
    1. COI'll mark your post as the answer and use all the info you have provided. If I can't reproduce any errors while debuging (which I have had in the past in this scenario) and take all the extra precautions (`Dispatcher.CurrentDispatcher + BeginInvoke + IsDisposed`) then hopefully everything will work in the production enviroment as well.
      singulars
    2. COI should perhaps mention that the window I'm talking about is a secondary one. The main window keeps running all the time and thus the application is alive. So on that basis, the Dispatcher itself will never be shutdown... What I would like to ask is if there might be any changes between .NET 3.5 SP1 and .NET 4 that might influence the ThreadPool scenario? I tried to replicate the error I had before with ThreadPool, but couldn't do it. I can't currently try to debug in .NET 3.5, because of a VS2010 bug, but I do know that the only thing that has changed is the framework version...
      singulars
    3. CODepends on how you go about creating the user control. If you don't intend to reuse it in other apps, then you'd probably add a new wpf UserControl to your solution, which consists of xaml and cs. In the xaml part you'll define the basic layout of things, mainly the container for the border items that represent progresses. And in the cs file you'l write code that actually creates new borders and places them into the container, also the update progress method...
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload