Question

I’ve got an ASP.NET page with a simple form. The user fills out the form with some details, uploads a document, and some processing of the file then needs to happens on the server side.

My question is – what’s the best approach to handling the server side processing of the files? The processing involves calling an exe. Should I use seperate threads for this?

Ideally I want the user to submit the form without the web page just hanging there while the processing takes place.

I’ve tried this code but my task never runs on the server:

Action<object> action = (object obj) =>
{
      // Create a .xdu file for this job
       string xduFile = launcher.CreateSingleJobBatchFile(LanguagePair, SourceFileLocation);

      // Launch the job                 
      launcher.ProcessJob(xduFile);
};

Task job = new Task(action, "test");
job.Start();

Any suggestions are appreciated.

Answer 1

You could invoke the processing functionality asynchronously in a classic fire and forget fashion:

In .NET 4.0 you should do this using the new Task Parallel Library:

Task.Factory.StartNew(() =>
{
    // Do work
});

If you need to pass an argument to the action delegate you could do it like this:

Action<object> task = args =>
{
    // Do work with args
};    
Task.Factory.StartNew(task, "SomeArgument");

In .NET 3.5 and earlier you would instead do it this way:

ThreadPool.QueueUserWorkItem(args =>
{
   // Do work
});

Related resources:

• Task Class
• ThreadPool.QueueUserWorkItem Method