Am 03.09.2010 um 14:47 schrieb Loritsch, Berin:
> I love SVN, and TortoiseSVN is a really good integration into
> Windows. My complaint has to do with Tortoise hijacking the local
> repository—particularly if it wasn’t the tool used to check the code
> out to begin with. I used to do Java code, and the SVN plugins for
> the major IDEs kept pace with SVN itself and this project.
> Now, I’m developing .Net and I’m not nearly so lucky any more. The
> plugin I have for Visual Studio uses a different version of the SVN
> client than TortoiseSVN. It’s a fact of life, it happens. The
> problem is that the SVN integration with Visual Studio breaks as
> soon as I touch the local repository with Tortoise. It breaks
> because the client version in my Visual Studio plugin is too old to
> work with that local repository. Tortoise SVN “upgrades” the local
> copy on me without warning me, telling me that is what it is doing,
> letting me cancel that decision, or respecting the fact I didn’t use
> Tortoise to check out the code to begin with.
As others have written, this is standard behaviour of Subversion when
changing the Subversion minor version.
The behaviour is documented in the release notes, including how to
downgrade (with Python), see the section named "Working Copy Upgrades"
extragroup GmbH - Karlsruhe
Geschäftsführer: Lars Busch
Registergericht: Amtsgericht Münster / HRB: 5624
Steuer Nr.: 337/5903/0421 / UstID: DE 204607841
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-03 16:35:25 CEST