SteveKing <firstname.lastname@example.org> wrote on 07/08/2005 12:03:28 PM:
> Ivan Zhakov wrote:
> > Hello,
> > I working on patch to TortoiseSVN that adds integration with
> > VisualStudio.NET. This will be regular VS.Net addin that add commands
> > to call TortoiseProc for SVN operations. Everything going OK. But I
> > have one question: Do you (developers first of all) like this idea? I
> > think it should be nice feature for TortoiseSVN.
> If you're willing to keep working on the addin and fix bugs which might
> arise, then we can include the addin into our sourcetree. But I won't do
> it if you can't/won't do that - I can't have stuff in the TSVN tree
> which has bugs and noone is willing/able to fix them.
> Also, which version(s) of VS.NET would the addin support?
In general, this is something I would like to see. Personally, I think
that SCC would be a better approach just so that it can work in more
IDE's. All that being said, regardless of the approach that is taken,
shouldn't it be a goal of whatever is done to do a bit more than just run
the commands? Aren't most people going to expect to see status
information? What about hooking into actions too? If I
rename/delete/copy/move a file in the IDE, I would expect the integration
to intercept that and run the appropriate Subversion command.
My company would be willing to financially support the development of a
tool that could do this, whether it is done by Stefan or someone else. Our
one requirement, until we can be convinced otherwise, is that it should
leverage the existing TortoiseSVN dialogs and actions as much as possible.
Ideally, it would even tap into the TSVN status cache as well.
Personally, I would like to see this all rolled into TSVN. If there were
a small "SCC Proxy" that could not be made GPL, so be it. But the rest of
the code could ideally be part of TSVN.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jul 8 18:15:36 2005