Hi
visual source safe remembers where a user checks out his files
--> suppose you checked out a file from
$/myprog/main.cs to a computer named MyPc in c:\temp
you can see this in the visual source safe interface
or in your user file in source safe ssinipath\users\<username>\ss.ini at
the bottom of the file
--> now suppose you also check the same thing out on another PC
named MyBackup to d:\code\
you can see this also in that file in source safe
CCNet wants to prevent this, by passing an argument to not remember the
working folder in source safe
--> that's were that line
Set C:\Temp\TempCCNet2 as the default folder for the project
$/_Dev/Source/... (Y/N) N.
comes from
hope this helps
with kind regards
Ruben Willems
On Thu, Dec 11, 2008 at 3:04 PM, Nos <[EMAIL PROTECTED]> wrote:
>
> Thanks very much for replying - can you shed some light on the
> behaviour described in the first paragraph? I'd like to understand
> whats going on re the message in the log. The Thoughtworks site
> describes the Working Folder: 'The folder into which the source should
> be retrived from VSS. If this folder does not exist, it will be
> automatically created'. The default behaviour is seemingly to say No
> to the request to set a new default folder yet source files still get
> put there?
>
> Thanks again
>
> On Dec 10, 10:27 am, Nickname <[EMAIL PROTECTED]> wrote:
> > I created a configuration which appeared to work. I set my working
> > directory in my config file to C:\Temp\TempCCNet1 which corresponded
> > to the working directory for a given project in source safe. If I make
> > changes and check them in, CruiseControl responds and the dlls's etc
> > get built/updated. If, however I change the working directory (in the
> > config file only) to say C:\Temp\TempCCNet2, CruiseControl responds by
> > copying the source files only over to this new directory (the dll's
> > etc in C:\Temp\TempCCNet1 still get updated as before). I get a
> > message in the log: Set C:\Temp\TempCCNet2 as the default folder for
> > the project $/_Dev/Source/... (Y/N) N.
> >
> > If I want to extend this so others including myself can use it I
> > presumably need to be able to build the results in an directory other
> > than where my Visual Studio login has it's working directory set?
> > Should the person that sets this type of system up have an additional/
> > separate set of credentials for source safe - one for the autobuild
> > process and one for individual development? Any thing that could throw
> > some light on this would be appreciated.
> >
> > Thanks
>
