[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Using Subversion with Visual Studio .NET

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-05-24 12:16:48 CEST

On 5/23/06, Foy, Sean <Sean.Foy@tycohealthcare.com> wrote:
> There is/was a bug in FrontPage Server Extensions, which VS.NET uses
> for Web Projects, involving files that begin with a period character.
> We stopped using Web Projects on my team in order to avoid having to
> use non-standard SVN admin directories. If you want to use Web
> Projects, then you may need a special build or to configure your SVN
> client tools (Ankh, Tortoise, whatever) specially.

I believe this is overcome by setting the SVN_ASP_DOT_NET_HACK
environment variable in Windows. You can do it at install time for
SVN, or do it manually. SVN clients using the 1.3 and higher
libraries should understand it just fine.

> > merits sticking with Visual Source Safe instead?
> VSS is really, really horrible. It sometimes lost data, telling us
> an hour after we did a "check in" that "write failed" or something.
> It is slow. It doesn't do atomic commits. It doesn't scale. It
> isn't maintained (although recently MS has decided to offer an
> alternative product, which they may or may not maintain). It
> doesn't work well for our Unix programmers. It's hard to integrate
> with other software, such as continuous integration servers or
> software defect tracking systems. I could go on, but I guess I've
> made the point that in my opinion, VSS has very little merit
> compared to anything else I've seen. VSS's only real competition
> is the practice of storing versions in directories whose name
> indicates the version of the software.

As a former VSS user and part-time VSS admin, I can only echo everyone
else's objections to the tool. It's simply not an acceptable solution
in 2006. When your backups fail and your database gets corrupted (and
it *will* get corrupted), it hurts. A lot. When we finally learned
that you had to do integrity checks weekly at least, the database was
large enough that it took 3 hours to run. And the "checks" often
can't repair the database.

I would have preferred using no version control over the mess VSS
turned into - and I was one of the people who pushed to get source
control, and advocated VSS most strongly, when that employer decided
we needed to set something up (at the time, in 1999, it was the only
solution that would work for us that management would approve, and we
didn't know how dangerous it was).

MS doesn't even use VSS, and haven't for many years. SVN has been
self-hosted for quite a while.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 24 12:18:12 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.