This post originated from an RSS feed registered with Java Buzz by Simon Brown. Original Post: How does .NET isolate web applications? Feed Title: Simon Brown's weblog Feed URL: http://www.simongbrown.com/blog/feed.xml?flavor=rss20&category=java Feed Description: My thoughts on Java, software development and technology. Latest Java Buzz Posts Latest Java Buzz Posts by Simon Brown Latest Posts From Simon Brown's weblog

I've been doing some digging around today trying to better understand how the .NET runtime isolates applications that share assemblies and I thought I'd post the links that I found useful. In the Java world, the Java EE specification has rules around how web applications are isolated from one another through the use of a hierarchy of classloaders. This, for example, is how you can have a singleton or static variable that doesn't get inadvertently shared between web applications running on the same application server/JVM. With multiple ASP.NET web applications running under a single IIS process, it's a similar story with .NET having a similar concept called AppDomains. Here are those links...

• What ASP.NET Programmers Should Know About Application Domains
• Application vs. AppDomain
• More on Jar Hell
• Programming with Application Domains and Assemblies

Hope you find the links useful!