ASP.NET application architecture: bet practice for lenghty background processes?
<p>I'll try to be brief. </p>

<p>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?</p>

<p>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...</p>

<p>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?</p>
