RE: Re: .svn vs _svn on VS.NET (ASP.NET)

I would just like to reiterate that there are millions of .net developers out there and a large portion of those are asp.net developers. Subversion is a great product that I feel is a strong alternative for these developers especially now that 1.0 is out) but *NOT* if they cannot use the product without changing the way they develop or utilizing a hack or custom build to achieve this (which will almost never fly in larger organizations - at least not where I am from).

Some people seem very adamant about this issue, but being new to this list and broaching the subject I immediately saw a lot of aggressive feedback on the topic. By the way, we still have to use VS.net 2002 on many, many apps so the prospect of Whidbey solving the problem is simply not factual (plus we'll be lucky if it releases this year).

I think Subversion is great and I hope to be able to use it in the future across our org rather than just my desktop.

-----Original Message-----
From: Ben Reser [mailto:ben@reser.org]
Sent: Monday, March 08, 2004 11:56 PM
To: dev@subversion.tigris.org
Subject: Re: .svn vs _svn on VS.NET (ASP.NET)

On Mon, Mar 08, 2004 at 04:39:44PM -0600, kfogel@collab.net wrote:
> Clearly, the ".svn" thing is causing a big problem for VS.NET users
> (actually, I thought it was only ASP.NET, but I'm fuzzy on exactly
> what each of these terms encompasses, so forgive me if I blunder).

I don't buy this. I think there's been very few people who have
actually said this problem is affecting them. I think there are a lot
of people saying this should be fixed, many of whom are admitting it's
not a problem they've encountered yet. In fact many of the people
arguing for it aren't even clear on what the problem is.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 12 02:25:50 2004