Databases
StackOverflow2013
Postsdbo
PORunning an asynchronous operation triggered by an ASP.NET web page request
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORunning an asynchronous operation triggered by an ASP.NET web page request
    primarykey
    data
    text
    <p>I have an asynchronous operation that for various reasons needs to be triggered using an HTTP call to an ASP.NET web page. When my page is requested, it should start this operation and immediately return an acknowledgment to the client.</p> <p>This method is also exposed via a WCF web service, and it works perfectly.</p> <p>On my first attempt, an exception was thrown, telling me:</p> <pre>Asynchronous operations are not allowed in this context. Page starting an asynchronous operation has to have the Async attribute set to true and an asynchronous operation can only be started on a page prior to PreRenderComplete event.</pre> <p>So of course I added the <code>Async="true"</code> parameter to the <code>@Page</code> directive. Now, I'm not getting an error, but the page is blocking until the Asynchronous operation completes.</p> <p>How do I get a true fire-and-forget page working?</p> <p><strong>Edit:</strong> Some code for more info. It's a bit more complicated than this, but I've tried to get the general idea in there.</p> <pre><code>public partial class SendMessagePage : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { string message = Request.QueryString["Message"]; string clientId = Request.QueryString["ClientId"]; AsyncMessageSender sender = new AsyncMessageSender(clientId, message); sender.Start(); Response.Write("Success"); } } </code></pre> <p>The AsyncMessageSender class:</p> <pre><code>public class AsyncMessageSender { private BackgroundWorker backgroundWorker; private string client; private string msg; public AsyncMessageSender(string clientId, string message) { this.client = clientId; this.msg = message; // setup background thread to listen backgroundThread = new BackgroundWorker(); backgroundThread.WorkerSupportsCancellation = true; backgroundThread.DoWork += new DoWorkEventHandler(backgroundThread_DoWork); } public void Start() { backgroundThread.RunWorkerAsync(); } ... // after that it's pretty predictable } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDamovisa
    1. USDamovisa
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORunning an asynchronous operation triggered by an ASP.NET web page request
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORunning an asynchronous operation triggered by an ASP.NET web page request
      1. USdavid valentine
      1. VTFavorite
    3. VO
      singulars
      1. PORunning an asynchronous operation triggered by an ASP.NET web page request
      1. USjmcd
      1. VTFavorite
    1. COHard to answer without seeing the code that calls this asynchronous operation.
      singulars
      1. PORunning an asynchronous operation triggered by an ASP.NET web page request
      1. USBryan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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