Perhaps this would help;
In BuildRunner.cs, selecting the temp build directory and retrieving the
source code is the reponsibility of GetSource() as below.
private string GetSource() {
string temp = Path.GetTempFileName();
File.Delete(temp);
Mark, it seems there is an issue with the output produced from VSS in the
History/Update list. If a file is added or removed, it is difficult to
ascertain where the file was added or removed to. You get a project name, but its not
a full path like an update, that looks like this:
Update file
Working
Copy Directory... instead of check i ng out to a different
place each time?
Mark Griffiths [EMAIL PROTECTED] wrote:
Yes. When you mentioned the SS GET updating the source,
I thought
How could have I missed such a rudimentary principle of
an SCC.
But alas
: Thursday, December 11, 2003 10:44 AM
To: [EMAIL PROTECTED]
Subject: RE: [Draconet-users] RE: Having a Specific Working Copy
Directory... instead of check i ng out to a different place each time?
---
This SF.net email is sponsored by: IBM Linux
Phil Knight [EMAIL PROTECTED] wrote:
Nick Robinson [EMAIL PROTECTED] wrote:
Phil Knight [EMAIL PROTECTED] wrote:
snip
Phil, what is this like in terms of performance? I am
thinking of my current situation, and to move the source
elsewhere after the GET would probably add
