title: What to do with long running processes on a ASP.NET MVC site?
body: <p>This program is used for taking data that has been imported and exported it line by line to normalized tables. It can take hours sometimes.</p>
  
  <p>How it works is</p>
  
  <ol>
  <li>Uses presses button to begin processing</li>
  <li>A call is made from jquery to a method on the MVC controller.</li>
  <li>That controller calls a DLL which then begins the long processing </li>
  </ol>
  
  <p>Only one person uses this program at a time.</p>
  
  <p>We are worried about it tying up a ASP.NET IIS thread. Would this be more efficient if instead of the web site running the code we could make a scheduled task that runs a EXE every 30 minutes to check and process the code..</p>
  
  <p>EDIT 1: After talking to a coworker the work around we will do for now is simply remove the button from the web site that processes and instead refactor that processing into a scheduled task that runs every 5 minutes ... if there are any comments about this let me know.</p>
  
  <p>The question is really about the differences between the web site running code vs. a completely separate EXE...IIS threads vs. processes... Does it help any ? </p>