RE: [Draconet-users] Nant build files

[Yves Reynhout]

You said it yourself: Use relative paths in your nant build script. The path to the nant file in draco.exe.config should also be relative. (I hope by temporary files you mean the files draco has fetched into a temporary directory). The easiest way to test this, is to create your build file in the root of your chosen source safe project and author your source-related tasks relatively to this root (source files will likely be siblings or children in this case). Then just copy this entire tree (on your local disk) to an arbitrary location and see if the build still succeeds (using nant on the command line). Regards, Yves Reynhout. From: Morrill, John [mailto:[EMAIL PROTECTED] Sent: woensdag 14 april 2004 17:54 To: '[EMAIL PROTECTED]' Subject: [Draconet-users] Nant build files   Nant build files require source files to be specified.  When draco gets the latest version of the code in source safe, it stores it in a temporary folder, then deletes it when the build is done.  So, how can we tell draco to use temporary files in the csc compile?   This is what Draco's help file says:   "Relative paths are recommended because they allow the module to be checked out to any location and successfully built. This is exactly what Draco.NET does; it creates a temporary directory, does a cvs checkout <module>, (or a Visual SourceSafe Get) and then executes your NAnt build script (causing the default target to be executed). The location of the temporary directory will typically be something like %SystemRoot%\Temp\tmp14DD.tmp."   I had considered creating a shadow folder in source safe, but I wasn't sure if this is what Draco's makers had in mind.  Any ideas?