Debugging an ASP.NET Website Extremely Slow with Several Thousands of Temporary ASP.NET Files

Question

My team is responsible for maintaining the legacy ASP.NET Webforms web application project.

We are currently using Visual Studio 2010, and the project is targeting the .NET Framework 4.0.

The project has over 200 ASCX controls and nearly 900 RESX resource files. It creates an ASP.NET temporary files folder that contains more than 2000 files.

Of these temporary files there are 121.cmdline files, 151. compiled files, 64.delete files, 121.err files (all of which are 0 bytes), 121.out files, 59.pdb files, 121. tmp files and 246. cs files.

When we start debugging a project, it seems to take forever to load it (about 5 minutes or so).

The debug output window displays many, many lines similar to:

'w3wp.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\project\c8633237\88f5a808\App_Web_snat3rsu.dll' 

These lines appear slowly, about once per second, until the first page is loaded.

As soon as the first page loads in the browser, the project's performance seems reasonable, but getting there seems like too long.

I am looking for suggestions on how I can improve load times for this project.

I am concerned that there is something fundamentally wrong with the project that needs to be eliminated because it seems unreasonable that it should take 5 minutes to load into the debugger.

Answer 1

It is normal to have load time (first compilation) with the number of resource files that you have. The first time it loads, it will precompile the material, so the second time you run it, it will be faster. I will let you try to implement what is on this site.

http://blog.lavablast.com/post/2010/12/01/Slash-your-ASPNET-compileload-time.aspx