-Original Message-
From: David Reed [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 12:45 PM
To: [EMAIL PROTECTED]
Subject: RE: [Draconet-users] VSS Working Directory
My question for Chuck & Co. is "You're already using NAnt. Why not use
the vssget task that's built i
From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Erv
> Walter
> Sent: 07 November 2003 16:37
> To: [EMAIL PROTECTED]
> Subject: RE: [Draconet-users] VSS Working Directory
>
>
> This has been discussed, but I don't know what the timeline will look
> l
olution of having your build file in SCC and specifying
relative paths is really the preferred solution!
Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erv
Walter
Sent: 07 November 2003 16:37
To: [EMAIL PROTECTED]
Subject: RE: [Draconet-users] V
This
has been discussed, but I don’t know what the timeline will look like.
In
the mean time, a common solution is to put your nant script *in* VSS with
your code and then have it work off of purely relative paths.
From: Chuck Bryan
[mailto:[EMAIL PROTECTED]
Sent: Friday, N
Hello Chuck,
Are you using absolute paths in your NAnt file?
If so, you may want to make your script portable by using relative
paths. The build script of NAnt is an example of this.
Example: Project.build located in D:\ProjectRoot\ contains a path
"D:\ProjectRoot\build".
Solution: Change thi
Chuck,
If you build your NAnt script such that paths are relative, it should all work fine.
If you have
Draco running on some server, the model is that everything needed to build must be
within the VSS
project, and be relative. However, if you needed to install something outside of this
const
