title: BackgroundWorker used within collection items
body: <p>I used a Backgroudworker to do some work in order to do some time consuming tasks. </p>
  
  <pre><code>public void ConnectDataProvider()
      {
          bgw = new BackgroundWorker();
          bgw.DoWork += new DoWorkEventHandler(bgw_DoWork);
          bgw.RunWorkerCompleted += new RunWorkerCompletedEventHandler(bgw_RunWorkerCompleted);
  
      }
  </code></pre>
  
  <p>Another method starts the background worker:</p>
  
  <pre><code>public void StartPolling()
      {
          bgw.RunWorkerAsync();
      }
  </code></pre>
  
  <p>Then I did the event handling:</p>
  
  <pre><code>void bgw_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e)
      {
          // do it over again
          StartPolling();
      }    
  
  void bgw_DoWork(object sender, DoWorkEventArgs e)
      {
          // do work
          WriteData();
      }
  </code></pre>
  
  <p>As you can see, I started the worker over on completion. Now this works for a single backgroundworker.</p>
  
  <p>Now I want a collection, and each item should perform this task. However with the concept above it will just keep on running in the first worker started, as it starts the worker over. I'm thinking, maybe a Timer in combination could solve the situation to give the other worker threads way. </p>
  
  <p>Is the BackgroundWorker still a good choice? Is it common to reuse the BackgroundWorker like I did?</p>
  
  <p><strong>EDIT 1:</strong> To clairify: The problem I'm facing is, that I need manage the collection each with their own BackgroundWorker. I was thinking about a timer, to set off request periodically from each item. This is where I'm stuck.</p>
  
  <p><strong>EDIT 2:</strong> See my own answer, I didn't solve this issue, but found that I can go along with timers to get what I wanted.</p>
  
  <p><strong>EDIT 3:</strong> To clarify (another try, I'm not good at that) what I wanted to achieve: I've got tracking objects, for gps tracking. I want to track a whole bunch of them, so one object per tracking device. They all need to be polled frequently. Ihad a BackgroundWorker set up for a single test object. I liked they way the Backgroundworker would tell me when it's done. But I couldn't get it working with all of the tracking objects. </p>
  
  <p>Now every tracking object has its own timer. This timer spawns a new thread and does the time consuming work (which I named DoWrite). No BackgroundWorker needed, as I dispose the timer and then create a new timer. That's all it does.</p>