Visual Studio + svn: Working copies on network drive or local?

Answer by Jim L for Visual Studio + svn: Working copies on network drive or...

October 29, 2009, 4:33 pm

Definitely local for the aforementioned performance reasons, although I'd say that probably goes for any language.Your cited reason for keeping them on the share is backups. If that's the only reason,...

View Article

Answer by adrianbanks for Visual Studio + svn: Working copies on network...

October 29, 2009, 4:39 pm

Go with option A. If you back-up your subversion repository by backing up your subversion server, there is no need to back up your working copies*. When changes are committed into SVN, they get...

View Article

Answer by Indeed is Trash for Visual Studio + svn: Working copies on network...

October 29, 2009, 4:34 pm

I've always found that there are security issues with running code from a network drive, so I'm gonna say go local and check in often. In addition if you start using tools like visualsvn or tortoise...

View Article

Answer by Otávio Décio for Visual Studio + svn: Working copies on network...

October 29, 2009, 4:23 pm

I would stick with option A for a simple reason: that way developers will be more likely to commit their changes instead of leaving working copies lingering around because they know they are being...

View Article

Answer by Dustin Getz for Visual Studio + svn: Working copies on network...

October 29, 2009, 9:39 pm

are you using C++? Compiling is slow enough, don't underestimate the effect of compile times on your productivity. There are lots of free backup solutions for your local workstations.At work we use TFS...

View Article