title: "Simple" WPF with scheduling actions
body: <p>I am trying to develop a simple application that must have GUI components. It will be a service in the taskbar tray but must query the database every few minutes to check for changes, then post to a web server the results. It will run 24/7.</p>
  
  <p>This is my first application, and so have been getting some help along the way from SO. When I first used the FluentScheduler, I had trouble (<a href="https://stackoverflow.com/questions/48114894/c-sharp-fluentscheduler-job-not-repeating">C# FluentScheduler Job not Repeating</a>) but got it working as a simple proof of concept with a console app.</p>
  
  <p>As I tried taking what I had learned and implementing it with my Windows Forms solution, I couldn't get it working at all because once it ran the <code>Application.Run(ThisForm);</code> command, the scheduler did nothing. Eventually while troubleshooting, I stumbled across this:
  <a href="https://github.com/fluentscheduler/FluentScheduler/issues/169" rel="nofollow noreferrer">https://github.com/fluentscheduler/FluentScheduler/issues/169</a></p>
  
  <blockquote>
    <p>I see that you're using the library from something like a Windows Forms/WPF application. Starting threads/tasks from a GUI application is a pain in the ***, maybe that's what's biting you. Fingers crossed to be something else, diving up on STA threads, dispatchers, synchronization contexts and alikes is no fun.</p>
  </blockquote>
  
  <p>So now I am left wondering what I am supposed to do? Am I supposed to develop the scheduled tasks as a console app leaving an API for a WPF application to communicate with, or am I supposed to work through the pain he is describing and make it work within WPF? </p>
  
  <p>As this is my first C# project, it seems pretty complicated to separate the two components, but am willing to learn if that is the right choice. I am still very early in the project just doing proof of concepts of each needed feature and so can easily switch to WPF, UWP, or whatever else is most appropriate. It will have minimal GUI, just a few forms to fill out username / password type stuff and options to sync. </p>
  
  <p>Even though this FluentScheduler has about a quarter million downloads, maybe there is a better one that doesn't suffer from the same limitations you could recommend.</p>