A website takes a long time to get started after building a solution

During the development process, our Asp.Net 4 website takes quite a while to get started after creating the project libraries.

We make quite a lot of the population of statics, etc., but not enough to justify the time it takes for the application (maybe 3-4 minutes).

We are not creating a website, only libraries and batch! = True in the compilation element in the .config file.

I will try to write some diagnostic data, but any other pointers will be useful

+6
optimization build
source share
4 answers

You can also try optimizeCompilations="true" in a web.config compilation session.

 <compilation debug="true" batch="false" optimizeCompilations="true" > 

My site also runs too long for the first time after compiling my dll.

+8
source share

We hope that the steps below will shorten your time.

Close the project, then delete the file "Visual Studio User Interface Settings (.suo)" and open the project

+1
source share

If you have many projects related to the solution, when you build, it will create EVERY project. if you have projects in which you do not make changes, it is permissible to delete the project itself and refer directly to the .dll.

0
source share

The right thing here is to use dotTrace or Dynatrace for the profile and understand what the problem is. It will tell you how long it takes to execute all your code.

Another potential problem is that your solution cannot find the appropriate libraries. Turn on the merge log view to determine if the assembly binding fails.

0
source share

All Articles