CODEWITHSUNDEEP
asp.netvisual-studio-2010visual-studio-2008debugging
oscilatingcretin
oscilatingcretin

Reputation: 10919

how to speed up and optimize compiler build of asp.net site when debugging

Visual Studio 2008/2010/ASP.NET:

How to speed up the delay after rebuilding the solution?

I like to detach my debugger while testing my changes or debugging issues that can be pinpointed by a simple strack trace.

After I fix a bug, I build the solution and then refresh the page.

There's that initial lag time that occurs after the rebuild before the web page displays.

After that, it's as fast as it should be. I heard that the application is loading up all the new DLLs during this time.

Is there any way to reduce the amount of this lag?

Upvotes: 2

Views: 2203

Answers (1)

Aristos
Aristos

Reputation: 66641

You can set the optimizeCompilations to true, and batch to false

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

batch=false says to asp.net to build if necessary only the page that you call. We set batch to true, only on release live site to so the asp.net compiles many pages at ones, and you may have a big delay but only ones...

The optimizeCompilations=true says that each page is not check for libraries updates each time its runs. This have a minor issue - if you change a global static function for example that is called from 4 pages, this 4 pages did not know that this function change, so you need to just open them and saved them, to force compiler to re-compile them. Or else they throw error because they did not check if something change - you must know that and updates them to force the re-compile.

reference : CompilationSection Class

Upvotes: 7

Related Questions