Hi All,
Apart from the obvious "social" problem as described in the last paragraph
of this message by Simon Large:
http://svn.haxx.se/tsvnusers/archive-2006-06/0023.shtml (i.e. someday
somebody will overwrite a file in the WC at the same time as somebody else),
are there any technical issues related to sharing a SVN repository in this
way?
Following a dramatic start to our first ASP.Net project (a *lot* of code was
accidentally overwritten while they were working locally and copying to dev
for testing), I managed to convince the other devs here to give SVN a go, it
worked brilliantly and we have been using SVN for the SQL scripts, ASP.Net
sites and .Net applications we develop for just on a year and it is working
fine.
Now that SVN has proved itself we want to now add our ASP classic sites to
SVN - at the moment these are worked on directly on the dev server either
via FTP or shared drive access. So obviously we already have the problem of
people overwriting other peoples work, but at least using SVN will give us
the ability to at least go back and see what the other persons work was.
We have tested using TSVN on a networked WC and it *seems* to work fine and
from the research I have done on the net I actually haven't found any
references to "Using a networked WC screwed up my source code". So I thought
I would just check here to be sure.
As a discussion point, how do others work on ASP classic (or PHP etc) sites
and manage to merge SVN into the workflow?
Thanks for any advice,
Chris Ormerod
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Jul 31 02:12:57 2006