Home/ Questions/Q 110947
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T02:18:26+00:00

I’ll try to be brief. What is the best practice for calling a routine

  • 0

I’ll try to be brief.

What is the best practice for calling a routine from an asp.net web application that initiates a lengthy ‘background’ process that must be run?

For example, I want to click a button on my webpage that says ‘Run data conversion’ (for example). This data conversion routine may take 20-40 minutes to run, so it seems to me putting all that code into a asp.net web page is not the way to go….there is no need to run this background process thru the IIS server. A sperate service or app etc seemx the way to go…

The web app, and the background process will both run on my dedicated Win2003 server so I have lots of options – but what is the best one?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. There are quite a few options, basically it boils down to you needing any sort of process that you can communicate with. The options I can think of off the top of my head are; a web-service running under another application pool; a windows service; a command-line process started by your ASP.NET code.

    The next question is how to communicate with the other process. If you’re using a database you could set up two common-tables that both processes can access. The website would place the request for work into a table that the second process would monitor. A second table could then be used for the results, which the web-site would monitor. Another option would be to use something like the Windows Communication Foundation (WCF) or .NET remoting to send events between the processes.

    • 0