Web Site takes forever to run in debug mode

  • Thread starter Thread starter Waldy
  • Start date Start date
W

Waldy

Hi there,
I have a VS 2005 Web Site project that is taking an age to
build or run. It takes about fifteen minutes to run in debug mode. Even if
I just select Build Page, Visual Studio hangs for about five minutes.
There are about 20 pages so far and about 50 references.

Does anyone have any ideas?
 
Mark Rae said:
Assuming things are installed in their default locations:

C:\Windows\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files

or

C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

Never done this and just looked in the folder. It is running at 237 MB and
has 13K files. Is it safe to delete all these files at any time (while IIS
is not running)?

Thanks
Lloyd Sheen
 
That solution makes no sense. That cache is there for a reason, so when it
needs to be reloaded it'll naturally take even longer to load the debugger
than before. Instead of doing that, try and tweak your IDE settings,
especially those that deal with the debugger (Options->Debugging). You could
for example check the "Enable Just My Code (Managed only)" setting so that
symbols aren't loaded until they are needed. You can also go to
Options->Debugging->Symbols and set a local folder to act as a symbol store
to cache symbols. Also, in your project settings, make sure your code isn't
being optimized.

Eliyahu Goldin said:
First thing, try to clear ASP.NET temporary directory.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net


Waldy said:
Hi there,
I have a VS 2005 Web Site project that is taking an age to
build or run. It takes about fifteen minutes to run in debug mode. Even
if I just select Build Page, Visual Studio hangs for about five minutes.
There are about 20 pages so far and about 50 references.

Does anyone have any ideas?
 
Back
Top