Subversion, TortoiseSVN, and Windows

I am in the process of evaluating SCM software and wondered if someone
could help me out.

All of our developers code in CFML. The box that hosts our development
code is a Windows 2000 server that runs both CFMX 6.1 and IIS 5.

The IIS and CF roots both point to the same directory on the server,
C:\www.

Currently we use no SCM software, so all developers map a drive to
C:\www on this server, and hence have no "working copy" directories,
other than their mappings to C:\www itself.

I have configured VSS in the past, where your "working copy" for
development can be the actual directory that is under source control, so
I'm
having a bit of a hard time wrapping my head around the newer SCM
concepts presented by Subversion and TortoiseSVN.

I can create a repository and connect to it with absolutely no problems.

I can then use TortoiseSVN to connect to the repository and import all
of our code from C:\www. My questions are as follows:

Can our developers somehow "share" a working copy, so that none of us
actually have to keep a local working copy?
Once I commit a changed file to the repository, how do I get the updated
version back into C:\www so it can be tested?

This particular phrase from the book is what I do not understand:

Now the repository contains this tree of data. Note that the original
/tmp/project directory is unchanged; Subversion is unaware of it. (In
fact,
you can even delete that directory if you wish.) In order to start
manipulating repository data, you need to create a new "working copy" of
the
data, a sort of private workspace. Ask Subversion to "check out" a
working copy of the repository's trunk directory.

What this tells me is that after I import C:\www into the repository, I
don't need it anymore. I understand that, and I understand creating a
working
copy, perhaps on my local machine, so that I can check out files and
make changes, and that the changes get committed back to the repository.
What I
do not understand is to which directory should I point my IIS and CF
roots, since C:\www is no longer needed.

I have given all the docs a thorough read and have Googled my eyeballs
out looking for answers, to no avail.

I am certain it's just a configuration problem somewhere. Any help is
greatly appreciated.

Thanks in advance,

Pat Wenke
Received on Thu Oct 21 16:16:56 2004