From what I've seen, there can be a problem with VS.NET and its web
project cache. Something with folders starting with a period. There
might be a problem with the FrontPage extensions - I'm not sure. It's
something very "Microsoft-ish" between VS.NET and IIS but I'm not really
clear what the problem is.
I compiled a _svn version for my own use for a long time. I've stopped,
mostly because compiling Subversion on Windows is a PITA. The folder
name is the administrative folder in the *working copy*, so it doesn't
affect other users. One user could use the _svn version and everyone
else use the normal .svn version - everything would be fine.
Since TortoiseSVN is the only product offering both versions, you're
really at their mercy unless you decide to compile Subversion yourself.
if you feel that compiling the SWIG bindings for Java is *fun*, by all
means just compile your own version.
I use the _svn version of TortoiseSVN for web projects and eSvn for all
Nick Bronson wrote:
> Hey everyone,
> Iíve recently been discussing using Subversion as our primary source
> control system at the company where I work and Iíve been given the ok to
> go ahead and set it up after running some successful tests on my local
> box, using TortoiseSVN as our primary access method.
> I noticed in the FAQ that there can be a problem with web applications
> and the .svn folder name, and I was wondering if someone could tell me
> what the problem is and what causes it in a bit more detail. It was a
> concern to me as we have been working on a number of large web
> applications that we need source control for but I have tested using
> subversion with our web apps, and publishing them from my local dev box
> to the pre-production server whilst they are under source control and
> there doesnít seem to be a problem at all that I can see.
> I ask because it would be hard to justify using Subversion if we have to
> change our workflow significantly, or use a custom version of the
> clients (using _svn instead of .svn) to do it. The custom client is out
> because another division in the company already uses subversion and we
> need to maintain cross compatibility.
> They have told me that they havnít come across any problems either, are
> we missing something?
Scanned for viruses by ClamAV
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jan 14 04:42:12 2005