问题
In development, our Asp.Net 4 website takes a fairly lengthy time to start after the project libraries are built
We do a fair amount of population of statics etc, but not enough to justify the length of time it takes the app to come up (probably 3-4 minutes)
We aren't building the website, just the libraries, and batch != true in the compilation element in the .config file.
I will try log some diagnostics, but any other pointers would be useful
回答1:
You can also try the optimizeCompilations="true", on the compilation session of web.config.
<compilation debug="true" batch="false" optimizeCompilations="true" >
My site also makes too long to run for the fist time, after I compile my dll's.
回答2:
Hope the below steps will reduce your time
Close your project then delete the 'Visual Studio Solution User Options (.suo)' file and reopen the project
回答3:
if you have a lot of projects linked to the solution, when you do a build it will build EVERY project. if you have projects that you aren't making changes to, it is acceptable to remove the project itself and reference directly to the .dll.
回答4:
The right thing to do here is to use either dotTrace or Dynatrace to profile and understand what is the problem. It will tell you how long it takes to execute all your code.
Another potential issue is that your solution is not finding the appropriate libraries. Turn on fusion log viewer to determine if there are any assembly binding failures.
来源：https://stackoverflow.com/questions/5553057/website-takes-a-long-time-to-start-after-solution-build