<div>
Have any code you can show? &nbsp;What about background worker control?
</div>

Capture.PNG

<div>
Thanks to everyone for your comments. 
Andy, your suggestion is to put both 9 &amp;&nbsp;10 into the same background worker and 9 will complete before 10 begins. I wasn't aware that I could do this. I thought that if I tried to run 10 as a background worker whilst 9 was still active that I would get a &quot;busy&quot; response. Are you saying that by submitting first 9 and then 10 to the same background worker that 10 will effectively be queued whilst 9 is in progress? If so this will solve my issue. Can you confirm that this is the case ? 
 
regards 
Pat
</div>

<div>
You have misunderstood a little. &nbsp;Code in your background worker runs like code anywhere else - synchronously 
In the work function of your background worker you will have: 
(pseudo code) 
 
DoWork() 
{ 
&nbsp; &nbsp; &nbsp;RunSQLStatement &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;//(populate datatable with result of the SQL statement) 
&nbsp; &nbsp; &nbsp; EmailResultsToUser &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;// &nbsp;(emails results of SQL statement) 
} 
and the section (function call) RunSQLStatement &nbsp;will finish before the section EmailResultsToUser starts executing
</div>

<div>
Thanks Andy and Pawel, 
the one piece on info that I think you are overlooking is that this is a rules based application. The application is looping through a transaction by sequence number and running commands associated with each sequence number before reading in the next sequence number. &nbsp;So in the example &nbsp;RunSQLStatement &amp;&nbsp;EmailResultsToUser will always be run separately since RunSQLStatement is sequence 9 and &nbsp;EmailResultsToUser is sequence 10. However I still need to ensure that sequence 9 completes before sequence 10 kicks off. &nbsp;To Answers some of the questions this is a WCF Service which has a webform application as a client and is running ASP 4.5. &nbsp;The WFC Service reads through the transaction processing each line before moving on to the next line. It reverts to the client every time it encounters a sequence number which is an input statement. &nbsp;There is no need for await and both seq 9 &amp;&nbsp;10 are completely independent but do need to be run in sequence. &nbsp;If as Andy has indicated that sequence 9 , the SQL Statement, &nbsp;(which could run for 5-10 minutes ) will complete before sequence 10 begins then I should not have an issue. However I would like to know how DoWork() handles this ? One cycle of the application will submit the SQL statement (seq 9) and the next cycle will submit the email Results statement (seq 10). Control will immediately return to the beginning of the transactions t whilst 9 &amp;&nbsp;10 are running in the background. Will &nbsp;seq 10 be scheduled by DoWork() until 9 is complete ? If not what is the process ? 
 
regards 
Pat
</div>

<div>
Was there anything wrong with mine? 
 
Just spawn off a thread, it's essentially kicking off another program and will run sequentially.
</div>

<div>
&gt;&gt;If as Andy has indicated that sequence 9 , the SQL Statement, &nbsp;(which could run for 5-10 minutes ) will complete before sequence 10 begins then I should not have an issue. 
 
Unless you create something asynchronous in seq. 9 then it will finish before seq. 10 can start. &nbsp;Why should it not do so. &nbsp;Do you ever worry about any other code you write? 
 
eg. 
bool b = true 
if b = true then 
&nbsp; message.show &quot;hello&quot; 
&nbsp; b = false 
end if 
 
I expect that to always display the message, I don't worry that maybe the line of code b=false runs before the if statement (which is what you are saying might happen with seq.9 and 10).
</div>

<div>
sounds as if the continueWith is exactly what you need; once the task completes, the continue with will fire your email sequence, so they in turn will both fire on a background thread but sequentially 
 
<a href="https://msdn.microsoft.com/en-us/library/dd321405%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396" rel="ugc">https://msdn.microsoft.com/en-us/library/dd321405%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396</a>
</div>

<div>
Hi All, 
Andy &amp;&nbsp;Kyle's solution seems the simplest. &nbsp; Just following on from Andy's example, If I were to put the logic into pseudocode it would look like this. 
 
Transaction_table. 
SeqNo &nbsp; &nbsp; &nbsp;Command &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submission Mode 
001 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RTVUSREML &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
002 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RTVITM &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
003 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RTVDTERNG &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
004 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
005 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
006 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
007 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
008 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CFGSQL &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
009 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RUNSQL &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Batch &nbsp; &nbsp; &nbsp; &nbsp; 
010 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;EMLUSR &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Batch &nbsp; &nbsp; &nbsp; 
011 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;GOTO 001 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
 
Logic 
// Read through transaction_table in sequence 
foreach (DataRow row in table.Rows) 
&nbsp;{ 
&nbsp; if submission mode =&quot;Interactive&quot; 

<div class="indent">
{ 
Call processInteractiveCmd(command) 
}
</div>
else 

<div class="indent">
{ 
Call processBackgroundCmd(command) 
}
</div>
 
Seq 1 through Seq 8 would run interactively 
Seq 9 would run in background 
Seq 10 would run in background after seq 9 completes 
Seq 11 would run interactively whilst 009 is running in background allow user to restart process and submit next request &nbsp; 
 
&nbsp;I'll test this out and get back with the results. thanks agin to everyone for their comments and examples 
regards 
Pat
</div>

<div>
NO NO NO. &nbsp;Please read carefully what I (and the others) have told you. 
That logic will run the two processes 9 and 10 asynchronously to one another. &nbsp;You need to put both those processes 9 and 10 together in the same thread.
</div>

<div>
If I start the background process before iterating through the transaction_table then won't this place both seq 8 &amp;&nbsp;9 in the same synchronous thread: 
 
Taking Kyle's example: 
ThreadStart work = runBackground 
Thread thread = new Thread(work); 
thread.Start(); 
 
 
 
// Read through transaction_table in sequence 
foreach (DataRow row in table.Rows) 
&nbsp;{ 
&nbsp; if submission mode =&quot;Interactive&quot; 
{ 
&nbsp;RunCommand(command); 
} 
else 
{ 
&nbsp;RunBackground(command); 
} 
 
 
private void runBackground(object sender, DoWorkEventArgs e) 
{ 
&nbsp; string cmd = (string) e.Argument; &nbsp; &nbsp; 
&nbsp; RunCommand(cmd); 
} 
 
private void runCommand(cmd) 
{ 
&nbsp; &nbsp; &nbsp; .. 
&nbsp; &nbsp; &nbsp; .. // Run all commands here 
&nbsp; &nbsp; &nbsp; .. 
}
</div>

<div>
Based on your logic no. &nbsp;Your logic as you describe it will execute steps 1 to 8 synchronously (wait for finish before continuing) then start an asynchronous process (returns immediately) for step 9 so step 10 is also asynchronously started whilst step 9 may or may not have finished. &nbsp;You must run steps 9 and 10 in the same thread one after the other. 
 
 
Transaction_table. 
SeqNo &nbsp; &nbsp; &nbsp;Command &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Submission Mode 
001 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RTVUSREML &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
002 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RTVITM &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
003 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; RTVDTERNG &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
004 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
005 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
006 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive 
007 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
008 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;CFGSQL &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
009/010 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RUNSQL then run EMLUSR &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Batch &nbsp; &nbsp; &nbsp; &nbsp; 
 
011 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;GOTO 001 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Interactive
</div>

<div>
Hi Andy, 
my understanding of the &quot;same&quot; thread is one where there is only one new Thread specified. In my last example the thread is created before looping through the transaction file. I am not in a position to do the following 
 

<div class="indent">
DoWork() 
&nbsp;{ 
&nbsp; &nbsp; &nbsp; RunSQLStatement &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;//(populate datatable with result of the SQL statement) 
&nbsp; &nbsp; &nbsp; &nbsp;EmailResultsToUser &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;// &nbsp;(emails results of SQL statement) 
&nbsp;} 

</div>
 
because I don't know where in the transaction file that I will encounter commands that need to be run in sequence on background thread. If &nbsp;you are saying that: 
&nbsp; 

<div class="indent">
ThreadStart work = runBackground 
&nbsp;Thread thread = new Thread(work); 
&nbsp;thread.Start(); 
 
Loop through transaction file 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- process transaction through either UI or background thread 
end loop 

</div>
 
is not processing the background commands in the same thread then can you suggest how I can do this given fact that any number of the transactions may be required to run in background in the sequence that they are read. 
 
regards 
Pat
</div>

<div>
Finally got it working and learned a few things about background worker. Thanks to Andy for your patience. In the end I moved each of the sequences that were to run as background jobs onto a list and then after the interactive processing was completed I called the background worker once only to process this list. &nbsp;For anyone else trying to run sequenced background tasks within an interactive process I will list the same code below which proves that it works. I'll leave this question open for a couple of days in case there are any further comments 
regards 
Pat 
 

<pre><code class="code-100 nolinks" id="code-20-42104802-1">using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using System.Threading;
namespace WindowsFormsApplication1

{
 public partial class Form1 : Form
 {
 public Form1()
 {
 InitializeComponent();
 }
 BackgroundWorker bg_Worker;
 public List&lt;BGWParms&gt; myParmsList;

 private void button2_Click(object sender, EventArgs e)
 {
 bg_Worker = new BackgroundWorker();
 bg_Worker.DoWork += new DoWorkEventHandler(bg_Worker_DoWork);
 bg_Worker.ProgressChanged += new ProgressChangedEventHandler
 (bg_Worker_ProgressChanged);
 bg_Worker.RunWorkerCompleted += new RunWorkerCompletedEventHandler (bg_Worker_RunWorkerCompleted);
 bg_Worker.WorkerReportsProgress = true;
 bg_Worker.WorkerSupportsCancellation = true;
 
 BGWParms myParms= new BGWParms(); // Parameters to pass to backgroundworker
 myParmsList = new List&lt;BGWParms&gt;(); // List of background jobs to run

 // Similute reading transaction file seq 1 - 11
 for (int i = 1; i &lt; 12; i++)
 {
 // Assume that seq 9 &amp; 10 are the ones that need to run in background thread
 // Seq 9 is a long running job and Seq 10 is a short running job but it cannot 
 // run until seq 9 is complete
 // 
 if (i == 9 || i == 10)
 {
 if (i == 9)
 {
 myParms.Seq = i;
 myParms.Sleep = 10000;
 myParms.Command = &quot;RUNSQL&quot;; // Simulate Seq 9 (Run Sql)
 }
 if (i == 10)
 {
 myParms.Seq = i;
 myParms.Sleep = 500;
 myParms.Command = &quot;EMLUSR&quot;; // Simulate Seq 10 (Email User)
 }
 // Add all background jobs to a background jobs list
 myParmsList.Add(myParms);
 myParms = new BGWParms();

 }

 else
 
 // All sequences except 9 &amp; 10 will run interactively 
 {
 string Message = &quot;Running interactivele - Seq= &quot; + i ;
 System.Console.WriteLine(Message );
 }
 }


 // Now the list of background jobs required are in myParmsList in the sequence
 // they are required to run in. We can now pass this list to the background worker
 // for processing

 bg_Worker.RunWorkerAsync(myParmsList); // Call backgroundWorker with list of jobs to run

 }
 
 public class BGWParms
 {
 public int Seq { get; set; }
 public string Command { get; set; }
 public int Sleep { get; set; }
 
 }

 
 void bg_Worker_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e)
 {
 }


 void bg_Worker_ProgressChanged(object sender, ProgressChangedEventArgs e)
 {
 }

 void bg_Worker_DoWork(object sender, DoWorkEventArgs e)
 {
 List&lt;BGWParms&gt; passedParmsList = e.Argument as List&lt;BGWParms&gt;; // Retrieve list of jobs to run
 BGWParms passedParms = new BGWParms(); // Create new passedParms object
 
 for (int j = 0; j &lt; passedParmsList.Count; j++) // Loop through List for No elements in list
 {
 passedParms = passedParmsList[j];
 Thread.Sleep(passedParms.Sleep);
 string Message = &quot;Running in background - Seq= &quot; + passedParms.Seq + &quot;; Command: &quot;+passedParms.Command + &quot;; Sleep= &quot; + passedParms.Sleep;
 System.Console.WriteLine(Message);
 }

 if (bg_Worker.CancellationPending)
 {
 // Set the e.Cancel flag so that the WorkerCompleted event
 // knows that the process was cancelled.
 e.Cancel = true;
 bg_Worker.ReportProgress(0);
 return;
 }
 
 //Report 100% completion on operation completed
 bg_Worker.ReportProgress(100);
 }

 }
}
</code></pre>
 &nbsp; 
 
 
Result of running code 
Running interactivele - Seq= 1 
Running interactivele - Seq= 2 
Running interactivele - Seq= 3 
Running interactivele - Seq= 4 
Running interactivele - Seq= 5 
Running interactivele - Seq= 6 
Running interactivele - Seq= 7 
Running interactivele - Seq= 8 
Running interactivele - Seq= 11 
Running in background - Seq= 9; Command: RUNSQL; Sleep= 10000 
Running in background - Seq= 10; Command: EMLUSR; Sleep= 500 
The thread '&lt;No Name&gt;' (0x23dc) has exited with code 0 (0x0). 
The thread '&lt;No Name&gt;' (0x1dac) has exited with code 0 (0x0). 
The thread '&lt;No Name&gt;' (0x1da8) has exited with code 0 (0x0).
</div>

<div>
Thanks to all for you assistance with this 
 
regards 
Pat
</div>

<div>
<div class="content wysiwyg-content">
I have a c# rules based application which is running a transaction which runs an SQL statement oven a large file. I want to run the final parts of the transaction as a background job. So for example seq 1 – 8 below are gathering data selection details and &nbsp;seq 9 – 10 are running the SQL statement and emailing the results back. Step 9 &amp;&nbsp;10 are independent steps and therefore need to be run synchronously in a background job. 
 
 
Seq &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;operation &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; comment 
1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Get user email &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive 
2 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Get list of items &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
3 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Get date range &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
4 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive 
5 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive 
6 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive 
7 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;.. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
8 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Configure SQL statement &nbsp; Interactive &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 
9 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Run SQL Statement &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; Background job synchronously, &nbsp;(populate datatable with result of the SQL statement) 
10 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Email results to user &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Background job synchronously, &nbsp;(emails results of SQL statement) 
 
This command will email the results to the user email address. It should only run once Seq 9 is complete 
 
11 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GOTO Seq 1 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Interactive 
 
I have tried looking at task.RunSynchronously &nbsp; but this seems to run 10 &amp;&nbsp;11 in UI rather than in a background task. I have also looked a Background worker but it doesn't seem to have the ability to run synchronously. Appreciate if someone can suggest the best way to achieve what I am trying to do. If you can give an example - that would be great. 
 
regards 
Pat
</div>
</div>

I have a c# rules based application which is running a transaction which runs an SQL statement oven a large file. I want to run the final parts of the transaction as a background job. So for example seq 1 – 8 below are gathering data selection details and  seq 9 – 10 are running the SQL statement and emailing the results back. Step 9 & 10 are independent steps and therefore need to be run synchronously in a background job.


Seq	operation	        comment
1	Get user email	                Interactive
2	Get list of items	                Interactive                
3	Get date range	                Interactive                
4	..	                                        Interactive
5	..	                                        Interactive
6	..	                                        Interactive
7	..	                                        Interactive                
8	Configure SQL statement   Interactive          
9	Run SQL Statement	        Background job synchronously,  (populate datatable with result of the SQL statement)
10	Email results to user           Background job synchronously,  (emails results of SQL statement)

This command will email the results to the user email address. It should only run once Seq 9 is complete

11	GOTO Seq 1	Interactive

I have tried looking at task.RunSynchronously   but this seems to run 10 & 11 in UI rather than in a background task. I have also looked a Background worker but it doesn't seem to have the ability to run synchronously. Appreciate if someone can suggest the best way to achieve what I am trying to do. If you can give an example - that would be great.

regards
Pat

Run tasks synchronously in background thread

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).