Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > ASP.NET 2.0 AppDomain recycling

Reply
Thread Tools

ASP.NET 2.0 AppDomain recycling

 
 
John Rivers
Guest
Posts: n/a
 
      10-13-2009
Hi

Since upgrading one web app to 2.0 the AppDomain recycles whenever
there is a change in the bin folder

This results in a new AppDomain being created and a full recompilation
of the web app

This takes around 20 seconds and uses about 75% cpu in the process

On the production server this is not a problem as changes to the bin
folder are rare

But whilst I am developing - being forced to wait 20 seconds again and
again and again

is extremely frustrating and interfering with my productivity

ASP.NET 1.1 had a really useful (for me) bug/feature where you could
load the same DLL again and again

as there is no way to unload a managed DLL this is technically a
memory leak - but only whilst developing
thus once a day a simple IISRESET would solve the problem

ASP.NET 2.0 has been redesigned partly to avoid this memory leak
problem

And that is my problem - I *want* the memory leak as it means I can
work quickly

Does anybody know, or can anybody think of a way to stop this unwanted
AppDomain recycling?

 
Reply With Quote
 
 
 
 
3P
Guest
Posts: n/a
 
      06-01-2010
Dnia 13-10-2009 o 15:57:28 John Rivers <> napisał(a):

> Hi
>
> Since upgrading one web app to 2.0 the AppDomain recycles whenever
> there is a change in the bin folder
>
> This results in a new AppDomain being created and a full recompilation
> of the web app
>
> This takes around 20 seconds and uses about 75% cpu in the process
>
> On the production server this is not a problem as changes to the bin
> folder are rare
>
> But whilst I am developing - being forced to wait 20 seconds again and
> again and again
>
> is extremely frustrating and interfering with my productivity
>
> ASP.NET 1.1 had a really useful (for me) bug/feature where you could
> load the same DLL again and again
>
> as there is no way to unload a managed DLL this is technically a
> memory leak - but only whilst developing
> thus once a day a simple IISRESET would solve the problem
>
> ASP.NET 2.0 has been redesigned partly to avoid this memory leak
> problem
>
> And that is my problem - I *want* the memory leak as it means I can
> work quickly
>
> Does anybody know, or can anybody think of a way to stop this unwanted
> AppDomain recycling?
>



You should look at <compile optimizeCompilations="true" batch="false">

I'm not sure about batch attribute now. First one needs a special download
from MS. It isn't in ASP.NET by default. At least it wasn't in 2.0.
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Accessing appDomain members from another appDomain mrajanikrishna@gmail.com ASP .Net 1 09-13-2008 09:15 PM
Calling from default AppDomain (native code) into another AppDomain (managed code), hosted by ASP.NET Dave Burns ASP .Net 0 01-12-2007 03:43 PM
Calling from default AppDomain (native code) into another AppDomain (managed code), hosted by ASP.NET Dave Burns ASP .Net 2 01-12-2007 03:41 PM
"viewstate is invalid for this page and might be corrupted" - why does worker process recycling cause this? Trevor Andrew ASP .Net 0 07-25-2003 04:58 AM
Viewstate Corrupt error message after "Worker Process" recycling Trevor Andrew ASP .Net 2 07-24-2003 01:34 PM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57