Web Site takes forever to run in debug mode

Web Site takes forever to run in debug mode

am 17.04.2008 15:29:48 von John Smith

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?

Re: Web Site takes forever to run in debug mode

am 17.04.2008 15:58:32 von Eliyahu Goldin

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" wrote in message
news:eWumd8IoIHA.2256@TK2MSFTNGP05.phx.gbl...
> 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?
>
>

Re: Web Site takes forever to run in debug mode

am 17.04.2008 17:09:05 von John Smith

"Eliyahu Goldin" wrote in
message news:%23DIkLNJoIHA.2160@TK2MSFTNGP06.phx.gbl...
> First thing, try to clear ASP.NET temporary directory.

Where exactly is this folder?

Re: Web Site takes forever to run in debug mode

am 17.04.2008 17:30:24 von mark

"Waldy" wrote in message
news:u7fJ9zJoIHA.4024@TK2MSFTNGP06.phx.gbl...

>> First thing, try to clear ASP.NET temporary directory.
>
> Where exactly is this folder?

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


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Re: Web Site takes forever to run in debug mode

am 17.04.2008 18:20:17 von Courtney

"Mark Rae [MVP]" wrote in message
news:%233$Q1$JoIHA.3804@TK2MSFTNGP02.phx.gbl...
> "Waldy" wrote in message
> news:u7fJ9zJoIHA.4024@TK2MSFTNGP06.phx.gbl...
>
>>> First thing, try to clear ASP.NET temporary directory.
>>
>> Where exactly is this folder?
>
> 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
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

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

Re: Web Site takes forever to run in debug mode

am 17.04.2008 18:33:45 von mark

"Lloyd Sheen" wrote in message
news:%23L$zvbKoIHA.1240@TK2MSFTNGP02.phx.gbl...

> Is it safe to delete all these files at any time (while IIS is not
> running)?


Yes.


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Re: Web Site takes forever to run in debug mode

am 17.04.2008 18:44:39 von Courtney

"Mark Rae [MVP]" wrote in message
news:OJkDPjKoIHA.4912@TK2MSFTNGP03.phx.gbl...
> "Lloyd Sheen" wrote in message
> news:%23L$zvbKoIHA.1240@TK2MSFTNGP02.phx.gbl...
>
>> Is it safe to delete all these files at any time (while IIS is not
>> running)?
>
>
> Yes.
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

Thanks, is there a way to cause this to happen on a schedule within IIS?

LS

Re: Web Site takes forever to run in debug mode

am 17.04.2008 18:53:37 von mark

"Lloyd Sheen" wrote in message
news:%23RvBXpKoIHA.5096@TK2MSFTNGP02.phx.gbl...

>>> Is it safe to delete all these files at any time (while IIS is not
>>> running)?
>>
>> Yes.
>
> Thanks, is there a way to cause this to happen on a schedule within IIS?

I don't think so, but it would be a fairly trivial matter to create a
Windows scheduled task to do it...


--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Re: Web Site takes forever to run in debug mode

am 21.04.2008 18:10:25 von John Smith

"Eliyahu Goldin" wrote in
message news:%23DIkLNJoIHA.2160@TK2MSFTNGP06.phx.gbl...
> First thing, try to clear ASP.NET temporary directory.

OK I've done that. What next?