Scott Hanselman

Clean up your Temp Files

February 16, 2007 Comment on this post [6] Posted in ASP.NET | Tools
Sponsored By

I was doing some tidying up on a website for a family friend recently. His ASP.NET application was taking longer and longer to start up. It also happened to use a lot of XmlSerializers, and of course, as an ASP.NET app, there's a lot of page-by-page compilation as he's not on 2.0 and doesn't use aspnet_compiler.

Additionally, there's some code that this client wrote that writes out temp files but doesn't clean up after themselves. When there's this many files in a folder, calls to GetTempFileName can block for many seconds.

Not only can "excessive temp file growth" cause pain at runtime, but it'll easily crush Explorer.exe's usefulness. It'll also become impossible to apply Attributes to the folder.

The point is, that there's a few folders that you need to watch out for file growth in.

I like to modify the options inside Microsoft Drive Cleanup using Shawn A. Van Ness's registry file. You can extensively modify what appears in the Drive Cleanup list, even adding your own file types and your own application-specific directories and files that you might want cleaned up.

Check out your own systems...drop out to a command prompt (cmd.exe) and do:

  • cd %tmp% and cd %temp% - You'll usually end up in C:\DOCUME~1\username\LOCALS~1\Temp.
    • At this point, I like to do the equivalent of a deltree and go up a directory and:
      • cd ..
      • rd Temp /s (it usually won't manage to delete the whole dir. Someone will have a file open and the final directory deletion will fail)
      • md Temp (in case it was deleted.)
  • Everything in %windir%\temp - There's lots of Perfmon counters in here, so you won't be able to delete everything. Often you can del *.* and anything that shouldn't be deleted is currently open.
  • If you are a developer, and have developed ASP.NET for years/months, clean up %windir%\Microsoft.NET\Framework\ <VERSION> \Temporary ASP.NET Files. I had 4 dozens sites in here.

Tidy up, my friends.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
February 16, 2007 23:54
I just run this perl script that cleans up my temp dirs --- and it's lightning quick!

use File::Find;

my $UserTemp;
$UserTemp = $ENV{Temp};
$WinTemp = $ENV{windir};

find(\&Wanted, $UserTemp);

find(\&Wanted, $WinTemp);

print "\n\tSUCCESS: \"$UserTemp\" has been cleared!";
print "\n\tSUCCESS: \"$WinTemp\" has been cleared!\n";

sub Wanted {
#print $File::Find::topdir."\n";
opendir(DIR,$File::Find::topdir) or return;
my $current = $_;
my @List=readdir(DIR);

if (-f $current) {
unlink $File::Find::name;

sub smash {
my $dir = shift;
opendir DIR, $dir or return;
my @contents =
map "$dir/$_",
sort grep !/^\.\.?$/,
readdir DIR;
closedir DIR;
foreach (@contents) {
next unless !-l && -d;
rmdir $_;
February 17, 2007 0:11

That's nothing! Find someone who hasn't run spyware on their computer. Holy bejeezuss. Figure 100+ if this person browses at all.
February 17, 2007 2:41
The other benefit of that Perl script I posted is that it doesn't get hung up on files that it can't delete (ususally b/c a process has some temp file locked). It just moves along to the next one.
February 17, 2007 3:38
Crap Cleaner (ccleaner)is the only way to fly for all kinds of sqeaky clean goodness. isnt it already on your tools list? if not, why not? :)
February 17, 2007 3:38
Crap Cleaner (ccleaner)is the only way to fly for all kinds of sqeaky clean goodness. isnt it already on your tools list? if not, why not? :)
February 19, 2007 21:38
REM ClearTemp.cmd

@echo off
del "%TEMP%\*.*" /s /f /q
for /d %%d in (%TEMP%\*) do rmdir "%%d" /s /q

del "%WINDIR%\TEMP\*.*" /s /f /q
for /d %%d in (%WINDIR%\TEMP\*) do rmdir "%%d" /s /q

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.