<p>In building an ASP.NET 3.5 WAP, I'm always frustrated by the feeling that no matter how I "isolate" or "encapsulate" bits of logic or UI I'm still going to bring down the whole site any time I need to update a single line of code. I may be misunderstanding how ASP.NET handles changes in the "bin" directory, but given the number of "why is my AppDomain unloading?" messages in the various groups this still seems like something to avoid.</p>

<p>Does anyone have any guidance and/or frameworks to truly modularize an ASP.NET 3.5 WAP so that logic and pages can be added/updated "in flight"? I Googled System.AddIn a bit, but it seems to be focused on WPF applications.</p>

<p>Thanks for your help!</p>

<p>James White</p>

This is really hard to achieve since .NET doesn't support unloading a type that has been loaded into the app domain.
One way to do it is playing around with app-domains, or having WCF do it for you.
Another would be implementing ayende's
hod code swapping
.
A third way would be putting logic in the dynamically compiled part (the ASPX). However the app will restart after a configurable amount of changes.