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

Re: Visual Studio Integration happiness

From: steven higgan <steven.higgan_at_gmail.com>
Date: Sat, 18 Sep 2010 20:31:49 +1200

On Sat, Sep 18, 2010 at 7:53 AM, Loritsch, Berin <bloritsch_at_dtri.net> wrote:
>> From: Andy Levy [mailto:andy.levy_at_gmail.com]
>> As I said in my post, I'm not sure what this buys you, unless
>> VisualSVN doesn't touch the WC *at all* with its own code and
>> exclusively goes through the TSVN DLLs.
> That's exactly what it does. All the merge/conflict/log/etc. dialog
> boxes are 100% TortoiseSVN, just integrated into VisualStudio.
> Essentially, I only have to worry about TortoiseSVN to make sure the WC
> is correct.

Think about this for a second,

VSVN knows about the state of your working copy, so how does it do that?

The only way VSVN could have knowledge around what is changed, added
or removed is if it has an implementation of a working copy client.

If you have difficulty believing me, then change a file from one of
your projects outside of visual studio and see for yourself that VSVN
will use a file-modified glyph for the file you changed in the file

VSVN as a tool is adequate, its not as polished as Ankh v2 - no
surprise there Ankh is built from the ground up to be integrated into
Visual Studio while the only thing that VSVN is doing is separating
money form your bank account for tooling that puts TSVN a open source
tool, inside Visual Studio - nothing more, and yet you still have the
same issue managing your subversion clients.

Steven H


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-18 10:32:03 CEST

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