BUG: XCOPY Deployment Enlarges Temporary ASP.NET Folder Size (310450)


The information in this article applies to:

  • Microsoft ASP.NET (included with the .NET Framework) 1.0
  • Microsoft ASP.NET (included with the .NET Framework 1.1)
This article was previously published under Q310450

SYMPTOMS

When you use XCOPY deployment to update .aspx and .ascx pages in a virtual directory, if you do not modify files that trigger the AppDomain to be unloaded, the dynamic-link library (.dll) files that the AppDomain references do not get deleted. This causes the Temporary ASP.NET Files folder to grow each time the .aspx or .ascx files are recompiled, which eventually causes a shortage of disk space.

CAUSE

This problem occurs because you cannot unload assemblies from an AppDomain in this version of the .NET framework; you must unload the entire AppDomain.

RESOLUTION

To work around this problem, ensure that the AppDomain is unloaded when you perform multiple XCOPY deployments on a Web server that has limited disk space. The following files trigger an AppDomain to be unloaded. To prevent the Temporary ASP.NET Files folder from growing in size, modify these files:
  • Global.asax
  • Web.config
  • Machine.config
  • Any file that you modify in the virtual directory's Bin folder

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Modification Type:MajorLast Reviewed:3/26/2003
Keywords:kbbug kbCompiler kbDeployment kbnofix kbreadme KB310450
©2002 Microsoft Corporation. All rights reserved.