Separate C# Project for Reporting - Best Practice? : <p>I have a few reports in an MVC C# Web project and they work fine. But I noticed that on the live site people tend to select large report date ranges and other search criteria which would return a fairly large data set.</p>

<p>As the whole site is on one IIS site in one project, this causes the rest of the site to hang until the report has finished execution.</p>

<p>I'm just wondering whats the best practice to handle this scenario?</p>

<p>Is it to move the reports to their own project with their own IIS site and somehow point to it from my main site?</p>

<p>Is it to make the reports async?</p>

<p>I could use view/stored procedures but I wanted to stay away from them.</p>
