Re: [NAnt-users] Cannot delete file '...\Temp\tmp12F.tmp\ResGen.exe'

[Collins, K. (GE Healthcare) <Kev...@ge...>]

Thanks for the suggestions.

 

1.	It's the standard Windows user "temp" path, so the name isn't
too long.  It's usually something like:

C:\Documents and Settings\builduser\Local
Settings\Temp\tmp12F.tmp\ResGen.exe.  Keep in mind that this works on
other PCs with the same path, and it works *sometimes* on this PC.  When
it does get past this file in this project, it only dies with a similar
error message on a different project later in the build (same error,
just a different tmp directory).

2.	Nothing else running.  And on my laptop I have Symantec running,
and it doesn't interfere.

 

I'm convinced that the sporadic nature of this (well, it happens ALL the
time ... but at different places in the build process) indicates that it
may be something else, like a timing issue.  Is it possible that the OS
hasn't finished releasing the ResGen file handle yet that NAnt used
before NAnt tries to delete the file?  In other words, does NAnt run in
a multi-threaded mode?  As far as I understand it, the NAnt binary
creates the tmp directory, copies the ResGen.exe binary to that
directory, copies the .resx files and referenced DLLs there, compiles
the resx files into the appropriate resources, copies it out, and then
tries to delete all of the files.  It is in the deletion that it's
failing, and it's always with regards to ResGen.exe.  It's just that
from one build to another it happens in different sub-projects.

 

________________________________

From: Bevan Arps [mailto:Bev...@rb...] 
Sent: Tuesday, July 22, 2008 5:02 PM
To: Collins, Kevin (GE Healthcare); nan...@li...
Subject: RE: [NAnt-users] Cannot delete file
'...\Temp\tmp12F.tmp\ResGen.exe'

 

Two thoughts come to mind - both long shots.

 

(i) How long is the path that you quote as
"...\Temp\tmp12F.tmp\ResGen.exe" - if your build folder is nested really
really deep, so deep the path exceeds 200 odd characters, you could have
a problem.

 

(ii) You've turned off your AntiVirus - what about any other
anti-malware software, say, Microsoft Defender or similar. Is there
anything else on the machine that is accessing that file?

 

Idea: Install Process Monitor from SysInternals
(http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) and
track activity on the machine. You'll be able to identify every access
to the file, by any process.

 

Hope this helps,

Bevan.

 


************************************************************************
******

"This message (and any files transmitted with it) are confidential and
may be legally privileged. If you are not the intended recipient please
notify the sender immediately and delete this message from your system.


This message does not necessarily reflect the views of the
Reserve Bank of New Zealand. If the recipient has any concerns about
the content of this message they should seek alternative confirmation
from the Reserve Bank of New Zealand."

************************************************************************
******