VisualSVN 7.1 adds support for multiple working copies within a single solution and brings an update to the latest regular (non-LTS) Apache Subversion 1.12 release.
See the changelog for the complete list of changes.
You can download the latest VisualSVN 7.1 build from the official download page. Please note that VisualSVN 7.1 supports Visual Studio 2019 only.
Users of Visual Studio 2017 and older versions can upgrade to VisualSVN 6.4 or 5.4 that also received an update to Apache Subversion 1.12.0. You can download them from the same official download page. Choose the appropriate download depending on your Visual Studio version:
- If you are using Visual Studio 2017, you should upgrade to VisualSVN 6.4. See the VisualSVN 6.4.0 changelog for the complete list of changes.
- If you are using Visual Studio 2015 or older, you should upgrade to VisualSVN 5.4. See the VisualSVN 5.4.0 changelog for the complete list of changes.
Multiple working copies within a single solution
VisualSVN 7.0 and older require the solution file and all the projects to be located under the same filesystem subtree in a single working copy. VisualSVN 7.1 introduces support for multiple working copies within a single solution.
All working copies in your solution now show up in the Pending Changes window, where all common operations such as Update and Commit can be performed on them using the context menu. Most of the global commands in VisualSVN's main menu and the traffic-light status in Solution Explorer respect the multiple working copies too.
While it is still generally recommended to follow a single working copy approach (which is not affected by the new functionality), support for multiple working copies enhances the VisualSVN plug-in's capabilities for web development projects and for projects with complex solution layout. It also comes in useful when migrating from other source control systems.
What’s new in Apache Subversion 1.12
The main changes introduced in Apache Subversion 1.12 are:
- Improvements to the conflict resolver. The interactive conflict resolver now may automatically handle scenarios with moved files and folders when tree conflict reports a "locally missing" item while merging.
- Various enhancements and bug fixes.
- Updates of the experimental features.
For the complete list of changes, please consider the Apache Subversion 1.12 Release Notes. Note that Apache Subversion 1.12 is a non-LTS release, which is the second of the new 6-month regular releases with an emphasis on introducing new features more quickly and with a shorter support period. See the details on the Apache Subversion Roadmap page.
Upgrading existing licenses to VisualSVN 7.1
All VisualSVN 7.0 licenses are eligible for a free upgrade to VisualSVN 7.1. VisualSVN 6.x licenses issued on or after December 4th, 2018 are eligible for a free upgrade, too.
The upgrade to VisualSVN 7.1 is free if you use VisualSVN under the Community license.
Note that upgrading to VisualSVN 6.4 and 5.4 with a valid 6.x or 5.x license is free and does not require a license upgrade.
You can purchase an upgrade to VisualSVN 7.1 using the online purchase form.