RE: [ndoc-devel] RE: [Nant-users] NDoc Initialize Failure

[David Reed]

Don, we're all happy guinea pigs, mostly.  (I finally buckled under pressure and temporarily took NDoc out of the CI scripts.)  Send me a zip of the installer or file set that you want tested and we'll put it under load.     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Donald Kackman Sent: Saturday, February 28, 2004 9:43 AM To: David Reed; 'NAnt User List (E-mail)' Cc: 'NDoc Developers' Subject: [ndoc-devel] RE: [Nant-users] NDoc Initialize Failure   David,   We’ve implemented a fix for this problem which should allow multiple instances of NDoc to operate concurrently without contention.   This fix will be part of the 1.3 version of NDoc (which will be going to beta soon).   Realizing that you may be reluctant to install pre-release software on your build machines, is there some way for you to test this fix in your build scenario? I can send you binaries, or an installer for the current stable (pre-beta) version.   Let me know.   Cheers   Don Kackman   PS We’ve opened a tracker item for this issue. You can view and add comment here: http://sourceforge.net/tracker/?func=detail&aid=905559&group_id=36057&atid=416078     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Reed Sent: Saturday, February 21, 2004 3:06 PM To: NAnt User List (E-mail) Cc: NDoc Developers Subject: [ndoc-devel] RE: [Nant-users] NDoc Initialize Failure   Ryan,   It would unfortunately seem to be so.  We put NDoc into our Draco-managed NAnt scripts yesterday for the first time and saw a couple of these.  :(  Love NDoc, but that's a kind of irritating not-safe-for-multithreading feature.  Example build failure:   C:\Sandbox\Build\WebApplication.build.xml(108,4):      [ndoc] Error building documentation. The process cannot access the file "C:\Documents and Settings\BuildUser.DEV\Application Data\NDoc\MSDN\xslt\syntax.xslt" because it is being used by another process. The process cannot access the file "C:\Documents and Settings\BuildUser.DEV\Application Data\NDoc\MSDN\xslt\syntax.xslt" because it is being used by another process.   I'm not sure exactly what that means yet, except that occasionally developers will have to re-launch builds that fails under concurrency (just like they do if a SQL timeout occurs during NUnit tests)... usually when some rocket scientist checks in code (late) during the mid-day rebuild of everything under the sun (got it whittled down to only 96 unique builds now).   On a brighter note, I can recommend strongly that you not use the ShowMissing* properties when running NDoc against ASP.NET assemblies or the *.chm output will not show the summaries at all (even the ones that are there) – but that seems to be an NDoc bug, not a NAnt bug because the GUI generated *.chm has the same problem.  It seems to be a derivation issue for classes that inherit System.Web.UI.Page (or classes derived therefrom).  Setting ShowMissing* to false in the GUI or NAnt script will at least permit the summaries that are defined to show up.  If anybody cares, I can zip up a file set and send it to the ndoc-devel list.  (I never noticed the unfortunate assonance of devel before, but there it is.)       From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cromwell, Ryan Sent: Friday, February 20, 2004 7:49 AM To: NAnt User List (E-mail) Subject: [Nant-users] NDoc Initialize Failure   We have a number of builds that kick off about the same time.  About half the time, the builds fail with the attached log… has anyone seen this issue before.  Is NDoc not safe to run concurrent?   Thanks…