Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • You effectively cannot use Thread.Abort. Search on SO to find some discussions about why. Commented Nov 28, 2013 at 18:11
  • Are you sure you want to do this in ASP.NET? It sounds like something that runs at the server and runs independently of client browsers. Commented Nov 28, 2013 at 18:13
  • @SteveWellens Yes, this is a standalone application and run at server Commented Nov 28, 2013 at 18:28
  • Can you describe a little more what you are doing please? I understand it like this: A user clicks a button and triggers a "request". You want requests to be processed one-after-the-other. Is that accurate and complete? Does the user wait for completion or not? Commented Nov 28, 2013 at 19:20
  • FYI: I removed the asp.net tag (and added C#) Commented Nov 29, 2013 at 1:44