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 hope this is a voice of reason rather than another blast of strong
opinion!
I favour the addition of an option for changing the working copy '.svn'
directory for the following reasons:
- If you want Subversion to become the default choice for version
control then it has to support Windows well. Like it or not Windows
does have a large market share and there are a lot of windows software
developers out there.
- Currently Subversion does not support the use of a major
development environment called Visual Studio .NET well when it is used
for web projects, which is one of the big areas Microsoft are pushing
.NET for.
- People who use Visual Studio for this purpose are not primarily
software developers in the traditional sense - they produce web sites
for which the back end coding is only a part of the project. They are
not interested in the finer points of the revision control system they
are using, they just want to get on with their work without Subversion
getting in the way. You cannot expect them to work around this issue,
they will abandon Subversion instead.
- They are used to using products which are easy to install and which
work pretty much out of the box.
- Users of Microsoft tools and platforms are generally slow to
upgrade. Waiting for the next version of .NET is not a solution.
- The fix Karl proposed appears to be straightforward with few
disadvantages. In particular, it hurts no-one and helps what could be a
growing group of Subversion users.
- Until this is fixed there won't be many people using Subversion for
web projects in VS.NET because they will see these endless threads on
the subject, get frightened and go elsewhere.
- There has to be more people interested in using VS.NET for web
projects than there are people sharing working copies between platforms.
I have to sell Subversion to our IT group soon and I really would like
to be able to tell them that it will all work beautifully and provide
them with a configuration utility to set the 'use _svn' option.
Currently I have to be honest and say it's great but...
This is not an invitation to share opinions on Microsofts marketing
methods, market share, quality of platform or development tools, in fact
anything to do with Microsoft or Linux or any other platform. It is
just an appeal for a calm evaluation of the impact of this problem and
for the implementation of a straightforward fix which doesn't require
the end user to do a code rebuild.
And for that fix to be in 1.0.1:-)
--
Martin Tomes
echo 'Martin x Tomes at controls x eurotherm x co x uk'\
| sed -e 's/ x /\./g' -e 's/ at /@/'
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 9 10:34:22 2004