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 *
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 a
Only kidding. That seemed to have *temporarily* resolved it for that
instance. I then started getting an identical error later in the build
process. So I completely disabled my Symantec virus protection
(unloaded the service). And I'm back to getting the same error on the
same file.
___
I thought so, but double checked. The 'bad' machine did not have the
Temp folder setup as an exclusion from filesystem protection. I set
that to be excluded, and this seems to have solved it. Thanks!
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behal
both machines have the same virus scanner?
both have the virus scanner set to ignore the temp folders used during the
builds?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Collins, Kevin
(GE Healthcare)
Sent: Tuesday, July 22, 2008 11:53 AM
To: nant
I'm building a multi-solution project on 2 different PCs. One is a
single processor laptop, the other is a quad-core, dual processor
workstation. The NAnt binaries and all of my source code are copied
from a source server. The build works fine on my slower laptop, but
after successfully compilin
