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

Re: any working Visual Studio 2005 SCC providers?

From: Johan Appelgren <johan.appelgren_at_gmail.com>
Date: 2005-12-21 17:07:50 CET

On 12/21/05, Toby Johnson <toby@etjohnson.us> wrote:
> Rev. Steve Klett wrote:
> > I have been trying to find a add-in for visual studio that supports
> > subversion. I saw on the tigris site there are some links, but one of
> > them doesn't supprt 2005 yet and the other appears to be a dead
> > project. So... anyone out there developing one? Using one?\
> There has historically been little community interest in developing such
> a thing because (a) until very recently, the Non Disclosure Agreement
> required to get the API prevented open-source development, and (b) the
> Microsoft SCC methodology is very centered around file locking, which is
> at odds with the Subversion copy-modify-merge concept.
>
> We had some developers who were also concerned about the lack of VS
> integration at first, but once they started using TortoiseSVN they never
> really looked back. They now prefer to do source control operations from
> within Explorer because the TSVN functionality is so much more than an
> SCC provider can do.

How do they handle renaming, moving and copying files within a
project? I haven't tried using Visual Studio and TSVN much, but I
found it hard to keep the project files in synch with the actual file
names and locations if I moved/renamed first with TSVN, or I couldn't
easily move/rename files with TSVN after I had done the rename/move in
Visual Studio. Is this a non-issue for everyone else?

/Johan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 25 00:02:46 2005

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.