Does Process.WaitForExit() Really Wait?

[Jonathan Wood]

I'll check this out. Thanks.

Jonathan

Have you tried running Process Monitor from Sysinternals.

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Only monitor File System Activity.
Then set up filter on path ending in the filename.

Run your program.

This should give you a dump of events related to the file.

 

[florin]

Or you can just run the "Handle" tool from Sysinternals (now bought by
Microsoft) which can show you who is having handles to a given file.
You can just run "handle.exe <my file name> >someLogFile.txt" before
you do the delete, in case the delete fails just look in the
someLogFile.txt to see who had that file open at that time. Once you
know who is to blame you will know how to fix/hack it.

florin