Mar 26, 2014 05:41 AM|AidyF|LINK
In terms of performance, if one gives an improvement over abother it will be measured in milliseconds which is irrelevant given the vast majority of your task is taken up generating the report. In general asp.net is not the best technology to process long-running
tasks for reasons already stated. If possible, what I would do is create a windows service that monitors a queue (database, MSMQ, folder on the drive, whatever) and all your asp.net code does is write to that queue giving the parameters for the report and
the service picks this up and does the processing. If you use something like a database to store the queue, your service can mark that the job is done and your asp.net code can look at the queue to see the job is done and retrieve the report from wherever
the service writes it to.