To optimize some server-side database calls, I decided to use System.Threading.Tasks.Task to parallelize several database calls, and then use Task.WaitAll () to get all the results, pack them and send them to the client via WCF . This seems to work well when testing on the dev web server in Visual Studio (cassini), but does not work when deploying to IIS. Profiling client calls (using firebug) shows that calls are routed to IIS, but the corresponding calls are not sent to SQL Server.
Has anyone experienced this? Is there a restriction on using tasks in IIS?
Raj r source
share