That is pretty funny. I didn't actually go into the details because it get kinda complicated; mostly cause it should work.
Maybe a little more background would help out here. Building the default target for nant does the following. 0.) Setup dir and debug flags 1.) Build everything (to some dir like 'build\nant-ver\debug\bin') 2.) Use the newly build stuff with the unit tests. (Since running the unit test against the loaded version of nant would not test the current code) The pdb file is locked because the debug version of nant is running (step 2); doing the unit tests. The unit tests depend on a build, which should already be done (and is in step 1). But the source files are all newer than the outputs so the build is done again. So in step 2 we are using the nant version that we are building to. This causes the file in use error. Now, with the shadow files support that we added this should not happen, but for some reason this doesn't seem to be working. I would guess that the appdomain isn't actually smart enough to move other files (like the pdb) into the shadow cache folder. But this may just be another bug. Does that make more sense? ----- Original Message ----- From: "Brian Deacon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 19, 2003 4:18 PM Subject: Re: [Nant-users] Problem installing Nant0.8.01 > Alright... I'll bite... what does the ziplib date bug have to do with > the pdb file staying locked? (Snippet from Chris' log here) ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
