This update fixes several vulnerabilities, some of which affect VisualSVN products in certain configurations. Updating to the new builds is recommended for all users.

The update to Apache Subversion 1.14.5 fixes a vulnerability CVE-2024-46901 that potentially can lead to a denial of service. This is a low-severity vulnerability, and exploiting it requires an attacker to have write access to the repositories.

The update to Expat XML parser 2.6.4 cumulatively fixes four vulnerabilities, two of which, CVE-2024-45491 and CVE-2024-45492, are high-severity and potentially can affect 32-bit installations of VisualSVN Server.

Update for VisualSVN Server

You can get the latest VisualSVN Server 5.4.3 version from the official download page.

For the full list of changes, see the VisualSVN Server 5.4.3 changelog.

Alternatively, choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 5.3.6 if you have version 5.3.x installed.

Version families older than VisualSVN Server 5.3.x are no longer supported, and patch-level updates are not available for them. It is strongly recommended that you upgrade to VisualSVN Server 5.4.3 if you are using any version family older than 5.3.x. Please read the article KB233: Upgrading to VisualSVN Server 5.4 before beginning the upgrade.

Update for VisualSVN (a plug-in for Visual Studio)

On the official download page, please select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.3.5
• If you use Visual Studio 2019, update to VisualSVN 7.4.5
• If you use Visual Studio 2017, update to VisualSVN 6.8.5
• If you use Visual Studio 2015 or older, update to VisualSVN 5.7.5

For the full list of changes, see the corresponding changelog entries for these plug-in versions: VisualSVN 8.3.5, VisualSVN 7.4.5, VisualSVN 6.8.5 and VisualSVN 5.7.5.

You can get the latest VisualSVN Server 5.4.2 version from the official download page.

For the full list of changes, see the VisualSVN Server 5.4.2 changelog.

Alternatively, choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 5.3.5 if you have version 5.3.x installed.

Version families older than VisualSVN Server 5.3.x are no longer supported, and patch-level updates are not available for them. It is strongly recommended that you upgrade to VisualSVN Server 5.4.2 if you are using any version family older than 5.3.x. Please read the article KB233: Upgrading to VisualSVN Server 5.4 before beginning the upgrade.

This update fixes multiple high-severity security vulnerabilities, some of which affect both the VisualSVN plug-in and VisualSVN Server. Therefore, updating to the new builds is strongly recommended for all users.

The update to Apache Subversion 1.14.4 fixes a high-severity vulnerability CVE-2024-45720. This vulnerability affects Windows-based Subversion command-line tools (e.g., svn.exe) and can result in remote code execution via command-line argument injection. Command line tools packaged with VisualSVN Server and with versions 5.x of the VisualSVN plug-in are affected by this vulnerability.

The update to Apache HTTP Server 2.4.62 and OpenSSL 3.0.15 cumulatively fixes 15 vulnerabilities. Most notable among them are CVE-2024-40898, CVE-2024-38474, CVE-2024-38475, CVE-2024-38476 and CVE-2024-5535, which have critical CVSS scores. Default VisualSVN Server installations are not affected by any of these vulnerabilities. VisualSVN for Visual Studio is potentially affected by CVE-2024-6119 which has a high severity score and can lead to a denial of service.

The update to Expat XML parser 2.6.2 cumulatively fixes 3 vulnerabilities, two of which, CVE-2023-52426 and CVE-2023-52425, affect up-to-date installations of VisualSVN Server and VisualSVN for Visual Studio and can potentially lead to a denial of service.

Update for VisualSVN Server

You can get the latest VisualSVN Server 5.4.1 version from the official download page.

For the full list of changes, see the VisualSVN Server 5.4.1 changelog.

Alternatively, choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 5.3.4 if you have version 5.3.x installed.

Version families older than VisualSVN Server 5.3.x are no longer supported, and patch-level updates are not available for them. It is strongly recommended that you upgrade to VisualSVN Server 5.4.1 if you are using any version family older than 5.3.x. Please read the article KB233: Upgrading to VisualSVN Server 5.4 before beginning the upgrade.

Update for VisualSVN (a plug-in for Visual Studio)

On the official download page, please select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.3.4
• If you use Visual Studio 2019, update to VisualSVN 7.4.4
• If you use Visual Studio 2017, update to VisualSVN 6.8.4
• If you use Visual Studio 2015 or older, update to VisualSVN 5.7.4

For the full list of changes, see the corresponding changelog entries for these plug-in versions: VisualSVN 8.3.4, VisualSVN 7.4.4, VisualSVN 6.8.4 and VisualSVN 5.7.4.

• Improvements in Markdown rendering
• Advanced backup creation policies
• IP-based restrictions for Basic Windows Authentication

This new release also includes many other improvements. For the complete list of changes, see the VisualSVN Server 5.4.0 changelog.

The upgrade to VisualSVN Server 5.4 is recommended for all users. We strongly advise reading the article KB233: Upgrading to VisualSVN Server 5.4 before beginning the upgrade.

You can download VisualSVN Server 5.4 from the main download page.

Improvements in Markdown rendering

The rendering of Markdown documents in the Repository Web Interface now fully supports the widely-adopted CommonMark specification of Markdown syntax. Additionally, the following improvements have been made to Markdown rendering in the Web UI:

• Added support for anchor links (also known as section links). You can now link directly to specific section headings in a Markdown file.
• Added support for the blockquote-based GFM alert syntax. You can use the alert syntax to emphasize important information. Currently five types of alerts are supported: Note, Tip, Important, Warning and Caution, which will now be rendered with distinctive icons and colors in the Web UI.
• Added support for the GFM task list syntax. The Web UI will now render a task list as a list of items with read-only checkboxes, which can be useful for to-do lists.
• Added support for syntax highlighting in fenced code blocks. To enable syntax highlighting for a fenced code block, specify the language name after the triple backticks/tildes (e.g., ```cpp) that mark the start of the code block.
• Added support for HTML tags. This allows you to include parts with raw HTML markup inside Markdown documents.

Advanced backup creation policies

VisualSVN Server 5.4 offers new policy settings for scheduled repository backup jobs, when you use the mixed full/incremental backup scheme. In particular, it now is possible to conditionally make full backups based on the quantity of accumulated incremental backups. This allows you to conditionally skip a full backup for a repository when this repository has not had any commit activity recently.

The new policy settings also allow you to greatly reduce the use of storage space and time spent on making backups, by having longer chains of incremental backups that can now span more than one week. This is especially beneficial when you back up extremely large repositories.

Learn more about advanced backup creation policies

More enhancements

A few other notable improvements in this version are listed below:

• IP-based restrictions for Basic Windows Authentication. In the Windows authentication mode, it is now possible to selectively allow Basic authentication only to specific IP addresses, by setting up IP-based restrictions. Instead of enabling or disabling the Basic Windows Authentication method for everyone, you can now enable it only for specific users that require it, while forcing all other users to use the more secure Integrated Windows Authentication.
• New Test-SvnRepositoryBackup cmdlet for verifying repository backups.
• New Get-SvnRepositoryBackup cmdlet for listing all backups created by a particular backup job and for displaying information about individual backup files.

View detailed changelog

Upgrading to the new version

Upgrading to VisualSVN Server 5.4 is recommended for all users. Please read the KB233: Upgrading to VisualSVN Server 5.4 article before upgrading.

The upgrade is free for all customers who have an active maintenance subscription for the Enterprise or Essential licenses. The upgrade is also free for all customers who use VisualSVN Server under the Community license.

This update fixes a number of security vulnerabilities, out of which only the low-severity vulnerability CVE-2024-0727 discovered in OpenSSL may potentially affect up-to-date versions of the VisualSVN plug-in for Visual Studio. Although this is a low-severity vulnerability, we recommend that you update your VisualSVN plug-in to the latest version.

Despite the fact that up-to-date versions of VisualSVN Server are not affected by the vulnerabilities fixed in this maintenance update, updating your VisualSVN Server installation is also recommended.

Update for VisualSVN Server

You can get the latest VisualSVN Server 5.3.3 version from the official download page.

Among other changes in this maintenance update, it also fixes several issues that can result in errors when remotely administering 5.1.x versions of VisualSVN Server. For the full list of changes, see the VisualSVN Server 5.3.3 changelog.

Version families older than VisualSVN Server 5.3.x are no longer supported, and patch-level updates are not available for them. If you are upgrading from VisualSVN Server 5.2.x or older, please read the article KB222: Upgrading to VisualSVN Server 5.3 before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

On the official download page, please select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.3.3
• If you use Visual Studio 2019, update to VisualSVN 7.4.3
• If you use Visual Studio 2017, update to VisualSVN 6.8.3
• If you use Visual Studio 2015 or older, update to VisualSVN 5.7.3

For the full list of changes, see the corresponding changelog entries for these plug-in versions: VisualSVN 8.3.3, VisualSVN 7.4.3, VisualSVN 6.8.3 and VisualSVN 5.7.3.

The update is recommended for all users.

Update for VisualSVN Server

You can get the latest VisualSVN Server 5.3.2 version from the official download page.

Version families older than VisualSVN Server 5.3.x are no longer supported, and patch-level updates are not available for them. If you are upgrading from VisualSVN Server 5.2.x or older, please read the article KB222: Upgrading to VisualSVN Server 5.3 before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

On the official download page, please select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.3.2
• If you use Visual Studio 2019, update to VisualSVN 7.4.2
• If you use Visual Studio 2017, update to VisualSVN 6.8.2
• If you use Visual Studio 2015 or older, update to VisualSVN 5.7.2

This update fixes a number of security vulnerabilities, out of which only the CVE-2023-4807 vulnerability discovered in OpenSSL may potentially affect up-to-date versions of VisualSVN Server. This vulnerability is currently rated as high-severity, according to its base score on the Common Vulnerability Scoring System scale. Although no specific ways have been currently found in which exploiting this vulnerability can adversely affect VisualSVN Server, installing this maintenance update for VisualSVN Server is strongly recommended.

Despite the fact that up-to-date versions of the VisualSVN plug-in for Visual Studio are not affected by the vulnerabilities fixed in this maintenance update, updating your VisualSVN plug-in to an appropriate newest version is also recommended.

Update for VisualSVN Server

You can get the latest VisualSVN Server 5.3.1 version from the official download page.

Among other changes in this maintenance update, it also fixes an issue that caused an upgrade to VisualSVN Server 5.3.x to fail if you had a TLS/SSL certificate with a SHA1-based signature installed on your VisualSVN Server. For the full list of changes, see the VisualSVN Server 5.3.1 changelog.

Version families older than VisualSVN Server 5.3.x are no longer supported, and patch-level updates are not available for them. If you are upgrading from VisualSVN Server 5.2.x or older, please read the article KB222: Upgrading to VisualSVN Server 5.3 before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

On the official download page, please select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.3.1
• If you use Visual Studio 2019, update to VisualSVN 7.4.1
• If you use Visual Studio 2017, update to VisualSVN 6.8.1
• If you use Visual Studio 2015 or older, update to VisualSVN 5.7.1

For the full list of changes, see the corresponding changelog entries for these plug-in versions: VisualSVN 8.3.1, VisualSVN 7.4.1, VisualSVN 6.8.1 and VisualSVN 5.7.1.

We also announce that VisualSVN Server 5.1.x and 5.2.x versions will reach their End of Support on September 30th, 2023. We are ending support for these version families because they use OpenSSL 1.1.1, which is going to reach its End of Life on September 11th, 2023.

Upgrading to the latest VisualSVN Server and VisualSVN plug-in is strongly recommended for all users:

• Download VisualSVN Server 5.3.
• Download VisualSVN 8.3 for Visual Studio 2022.
• Download VisualSVN 7.4 for Visual Studio 2019.
• Download VisualSVN 6.8 for Visual Studio 2017.
• Download VisualSVN 5.7 for Visual Studio 2015 and older.

The new VisualSVN Server and VisualSVN plug-in versions are fully interoperable with each other and are also compatible with previous versions, so you can upgrade the server and the plug-in in any order. Please see the Upgrade and compatibility notes sections below for the respective VisualSVN products.

Transition to OpenSSL 3.0

OpenSSL 3.0 is the latest Long-Term Support (LTS) release of the OpenSSL library, which is used to secure network communications and implement the SSL/TLS protocols. The transition to OpenSSL 3.0 is transparent to end users as it does not alter the core functionality of VisualSVN products.

Previous versions of VisualSVN products have been using OpenSSL 1.1.1. With OpenSSL 1.1.1 reaching its End of Life on September 11th, 2023, the upgrade to OpenSSL 3.0 ensures that VisualSVN products ship with an up-to-date and actively maintained OpenSSL version. Because OpenSSL 3.0 is a major release, we are releasing this upgrade in the form of new minor versions of VisualSVN products, rather than as patch versions.

Upgrade for VisualSVN Server

The upgrade to OpenSSL 3.0 is the only change introduced in VisualSVN Server 5.3. In all other respects, VisualSVN Server 5.3.0 is identical to VisualSVN Server 5.2.0.

Upgrading to VisualSVN Server 5.3 is recommended for all users. You can download VisualSVN Server 5.3 from the main download page.

Upgrade and compatibility notes for VisualSVN Server

The upgrade to VisualSVN Server 5.3 is easy and straightforward, especially when upgrading from a 5.2.x version, but we strongly advise reading the article KB222: Upgrading to VisualSVN Server 5.3 before beginning the upgrade.

Importantly, VisualSVN Server 5.3 remains fully compatible with Subversion clients based on OpenSSL 1.1.1.

Upgrade for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• Users of Visual Studio 2022 should upgrade to VisualSVN 8.3.
• Users of Visual Studio 2019 should upgrade to VisualSVN 7.4.
• Users of Visual Studio 2017 should upgrade to VisualSVN 6.8.
• Users of Visual Studio 2015 or older should upgrade to VisualSVN 5.7.

The upgrade to OpenSSL 3.0 is the main change introduced in the new plug-in versions, with only VisualSVN 8.3.0 having several additional changes.

You can download an appropriate VisualSVN version from the official download page.

Upgrade and compatibility notes for the VisualSVN plug-in

The new VisualSVN plug-in versions are compatible with any Subversion server that supports TLS 1.2 or higher. If you have a reasonably up-to-date Subversion server, it can be expected to support the required version of the TLS protocol. VisualSVN Server supports TLS 1.2 starting from version 3.2.0.

Other than that requirement, the new plugin versions are fully compatible with all up-to-date versions of VisualSVN Server, regardless of the OpenSSL version used in the server. The new plugin versions are also fully compatible with any reasonably up-to-date version of TortoiseSVN.

End of Support for VisualSVN Server 5.1.x and 5.2.x

VisualSVN Server 5.1.x and 5.2.x versions will reach their End of Support on September 30th, 2023. We are ending support for these version families because they use OpenSSL 1.1.1, which is going to reach its End of Life on September 11th, 2023.

After September 11th, 2023, the 5.1.x and 5.2.x version families of VisualSVN Server will not receive any OpenSSL-related maintenance updates, but may still receive other maintenance updates until September 30th, 2023.

Maintenance updates for VisualSVN Server 5.1.x and 5.2.x

We recommend that you upgrade your VisualSVN Server directly to the latest VisualSVN Server 5.3.0. However, if you currently use VisualSVN Server 5.1.x or 5.2.x and cannot upgrade to VisualSVN Server 5.3.0 at the moment, you can opt for a smaller patch-level update to VisualSVN Server 5.1.6 or 5.2.1 respectively, depending on your current version.

The VisualSVN Server 5.1.6 and VisualSVN Server 5.2.1 versions are patch-level updates for the respective VisualSVN Server 5.1.x and 5.2.x version families, and contain a regular maintenance update to OpenSSL 1.1.1v, which fixes the CVE-2023-3817, CVE-2023-3446 vulnerabilities. Although these OpenSSL vulnerabilities do not affect up-to-date VisualSVN products, updating at least to these intermediary versions is recommended.

• Showing effective access permissions
• Password guessing attack protection
• Scheduled verification of repository backups
• Improved repository backup performance

This new release also includes many other improvements. For the complete list of changes, see the VisualSVN Server 5.2.0 changelog.

The upgrade to VisualSVN Server 5.2 is recommended for all users. We strongly advise reading the article KB214: Upgrading to VisualSVN Server 5.2 before beginning the upgrade.

You can download VisualSVN Server 5.2 from the main download page.

Showing effective access permissions

Effective access permissions are the resultant access permissions that a specified user has to a specified path, based on the combined effect of all the applicable access rules set in VisualSVN Server.

VisualSVN Server 5.2 now has a feature called Effective Access that makes it easier for the administrator to check whether the access rules are configured correctly and produce the intended result. It can be helpful for auditing and troubleshooting purposes.

Learn more about effective access permissions

Password guessing attack protection

VisualSVN Server 5.2 adds a feature that protects user credentials from password guessing attacks, such as brute-force or dictionary attacks. It works by temporarily blocking requests from IP addresses that fail to authenticate multiple times within a short period of time.

Learn more about password guessing attack protection

Scheduled verification of repository backups

VisualSVN Server administrators can now create 'Verify Backup' jobs for automatic verification of repository backups. This kind of job verifies that backups created by backup jobs are readable and restorable.

Learn more about the Verify Backup Jobs

More enhancements

A few other notable improvements in this version are listed below:

• Significantly improved repository backup performance. VisualSVN Server 5.2 creates backups up to 5 times faster and with lower CPU usage, although with a slightly reduced compression ratio.
• Added an option to specify the size of the private key for the TLS/SSL server certificate.
• Revamped the full/incremental backup job scheme selection in VisualSVN Server Manager.
• New run hook subcommand to launch arbitrary programs, with the --no-wait option for asynchronous execution.
• The check-logmessage hook subcommand now supports regular expression matching with the --regexp option.

View detailed changelog

Upgrading to the new version

Upgrading to VisualSVN Server 5.2 is recommended for all users. Please read the KB214: Upgrading to VisualSVN Server 5.2 article before upgrading.

The upgrade is free for all customers who have an active maintenance subscription for the Enterprise or Essential licenses. The upgrade is also free for all customers who use VisualSVN Server under the Community license.

The update to OpenSSL 1.1.1u fixes a number of security vulnerabilities. However, none of these vulnerabilities affect up-to-date versions of either the VisualSVN plug-in or VisualSVN Server.

Additionally, we have finished updating the VisualSVN plug-in to APR Util 1.6.3, by now also including this change into the plug-in versions intended for earlier versions of Microsoft Visual Studio. The update to APR Util 1.6.3 fixes the CVE-2022-25147 vulnerability, which is currently rated as medium severity. However, this vulnerability also does not affect up-to-date versions of VisualSVN products.

Despite the fact that the vulnerabilities fixed in this maintenance update do not affect up-to-date versions of the VisualSVN plug-in or VisualSVN Server, updating to the new builds is recommended for all users.

Update for VisualSVN Server

Get the latest VisualSVN Server 5.1.5 version from the official download page. For the list of changes, see the VisualSVN Server 5.1.5 changelog.

VisualSVN Server version families earlier than 5.1.x are no longer supported, and maintenance updates are not available for them. If you are using VisualSVN Server version family 5.0.x or earlier, it is strongly recommended that you upgrade to VisualSVN Server 5.1.5. If upgrading from VisualSVN Server version family 5.0.x or earlier, please read the KB204: Upgrading to VisualSVN Server 5.1 article before the upgrade.

Update for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.2.1.
• If you use Visual Studio 2019, update to VisualSVN 7.3.9.
• If you use Visual Studio 2017, update to VisualSVN 6.7.8.
• If you use Visual Studio 2015 or older, update to VisualSVN 5.6.8.

You can get the latest version of the VisualSVN plug-in, appropriate for your Visual Studio release, from the official download page.

Upcoming update to OpenSSL 3.0

The OpenSSL 1.1.1 version family, which is currently used by VisualSVN products, will reach End of Life in September of 2023. We are currently actively working on updating VisualSVN products to OpenSSL 3.0. Releases of VisualSVN products with an update to OpenSSL 3.0 are expected by the end of summer of 2023.

For the complete list of changes, see the VisualSVN 8.2.0 changelog.

You can download the latest VisualSVN 8.2 build from the official download page.

Support for Visual Studio on ARM64

VisualSVN 8.2 enables Subversion integration in Visual Studio 2022 in native ARM64 environments. The new version of the plug-in supports both x64 and ARM64 versions of Visual Studio with a single universal VSIX installation package.

To get started with VisualSVN 8.2 on ARM64, please also install TortoiseSVN for ARM64, which is available from the download page.

Upgrading existing licenses to VisualSVN 8.2

All VisualSVN 8.x licenses are eligible for a free upgrade to VisualSVN 8.2. The upgrade to VisualSVN 8.2 is also free if you use VisualSVN under the Community license.

If you don't qualify for a free upgrade, you can purchase an upgrade to VisualSVN 8.2 using the online purchase form.

The update to Apache HTTP Server 2.4.57 fixes the critical-level CVE-2023-25690 vulnerability found in the mod_proxy module. Although this module is shipped with VisualSVN Server, it is not loaded or enabled by default. Therefore, this vulnerability does not affect VisualSVN Server installations unless the module was manually enabled by the administrator. Another vulnerability fixed in this update—CVE-2023-27522—is related to the mod_proxy_uwsgi module, which is not shipped with VisualSVN Server.

The update to APR Util 1.6.3 fixes the critical-level CVE-2022-25147 vulnerability. This vulnerability also does not affect non-customized installations of VisualSVN Server, because VisualSVN Server does not use the functions provided by APR Util in a way that would allow this vulnerability to be exploited.

Although these vulnerabilities do not affect non-customized installations of VisualSVN Server, it is nevertheless strongly recommended that you update to the new VisualSVN Server 5.1.4 build.

Update for VisualSVN Server

You can get this latest VisualSVN Server version from the official download page.

VisualSVN Server version families earlier than 5.1.x are not supported, and maintenance updates are not available for them. If you are using any version family earlier than 5.1.x, it is strongly recommended that you upgrade to VisualSVN Server 5.1.4. When upgrading from a version family earlier than 5.1.x, please read the KB204: Upgrading to VisualSVN Server 5.1 article before the upgrade.

You can download the latest VisualSVN Server builds from the main download page.

Meanwhile, VisualSVN Server continues to be actively developed. We continue to provide updates and support for VisualSVN Server 5.1.x, which is the most recent version family. What is more, we are working on substantial improvements and exciting new features that are going to be introduced in the next updates.

Upgrade and compatibility concerns

The upgrade procedure is straightforward and in the majority of cases only requires downloading and running the installer of the latest version of VisualSVN Server. However, it is strongly recommended that you read the article KB204: Upgrading to VisualSVN Server 5.1 before beginning the upgrade.

This update fixes a number of security vulnerabilities, some of which may affect both the VisualSVN plug-in and VisualSVN Server. Therefore, updating to the new builds is recommended for all users.

Versions of VisualSVN Server prior to this update are affected by the moderate-severity CVE-2006-20001 vulnerability. It allows an authenticated attacker to perform a denial-of-service attack using a specially crafted request to the server. The underlying issue has been fixed in Apache HTTP Server 2.4.55.

As for the vulnerabilities fixed in OpenSSL 1.1.1t, the VisualSVN plug-in and default installations of VisualSVN Server are not affected by the high-severity CVE-2023-0286 vulnerability. However, versions of the VisualSVN plug-in and VisualSVN Server prior to this update can potentially be affected by the moderate-severity CVE-2022-4450 vulnerability.

Update for VisualSVN Server

Get the latest VisualSVN Server 5.1.3 version from the official download page. For the list of changes, see the VisualSVN Server 5.1.3 changelog.

Alternatively, choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 5.0.4 if you have version 5.0.x installed.
• VisualSVN Server 4.3.11 if you have version 4.3.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 5.1.3 if you are using any version family older than 4.3.x. Please read the KB204: Upgrading to VisualSVN Server 5.1 article before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.1.1.
• If you use Visual Studio 2019, update to VisualSVN 7.3.8.
• If you use Visual Studio 2017, update to VisualSVN 6.7.7.
• If you use Visual Studio 2015 or older, update to VisualSVN 5.6.7. Note that VisualSVN 5.6.7 is still using the Expat XML parser 2.2.10.

Get the latest patch version of VisualSVN, appropriate for your Visual Studio release, from the official download page.

For the complete list of changes, see the VisualSVN 8.1.0 changelog.

You can download the VisualSVN 8.1.0 build from the official download page.

Better integration with the Open Folder (Folder View) mode

We improved how VisualSVN integrates with the Open Folder mode in Visual Studio. Now all file and folder additions, renames and deletes are automatically tracked and scheduled for the next commit.

As a separate enhancement, the auxiliary .svn folder is no longer displayed in this mode and is no longer searched, as this was cluttering the search results.

IPv6 support

VisualSVN 8.1 adds support for the IPv6 protocol. All the built-in VisualSVN features such as the Add Solution to Subversion wizard are now capable of communicating using IPv6. This makes it possible to use the VisualSVN plug-in on IPv6-only networks and with IPv6-dependent services such as Microsoft DirectAccess.

Upgrading existing licenses to VisualSVN 8.1

All VisualSVN 8.x licenses are eligible for a free upgrade to VisualSVN 8.1. The upgrade to VisualSVN 8.1 is also free if you use VisualSVN under the Community license.

If you don't qualify for a free upgrade, you can purchase an upgrade to VisualSVN 8.1 using the online purchase form.

Download the latest VisualSVN Server builds at the main download page.

The reason behind the upcoming End of Support for versions 4.2.x of VisualSVN Server is that these versions are linked with the 1.10.x releases of Apache Subversion. However, the 1.10.x Long-Term Support release line of Apache Subversion has reached its End of Life in accordance with the Apache Subversion’s release life-cycle.

Meanwhile, the whole product family of VisualSVN Server continues to be actively developed. We continue to provide updates and support for versions 4.3.x, 5.0.x and 5.1.x of VisualSVN Server.

What is more, we are working on substantial improvements and exciting new features that are going to be introduced in the next updates.

Upgrade and compatibility concerns

The upgrade procedure is straightforward and in the majority of cases only requires downloading and running the installer of the latest version of VisualSVN Server. However, it is strongly recommended that you read the article KB204: Upgrading to VisualSVN Server 5.1 before beginning the upgrade.

The update is recommended for all users of VisualSVN for Visual Studio 2022.

You can get the latest version of VisualSVN on the official download page.

• Uploading files in the web interface
• Native HTTP Strict Transport Security (HSTS) support
• Generating a new private key for TLS/SSL certificates
• Server-wide access rules for Subversion authentication

There are several other improvements in the new release. For the complete list of changes, see the VisualSVN Server 5.1.0 changelog

The upgrade to VisualSVN Server 5.1 is recommended for all users. We strongly advise reading the article KB204: Upgrading to VisualSVN Server 5.1 before beginning the upgrade.

Download VisualSVN Server 5.1 from the main download page.

Uploading files in the web interface

VisualSVN Server 5.1 adds support for uploading files into Subversion repositories right from the web interface.

The new feature enables quick and simple file additions and modifications. New files and modified versions of existing files can be uploaded directly into a repository without having to use a working copy and a Subversion client.

Being able to upload and modify files from a web browser introduces new usage scenarios for VisualSVN Server and should be useful for less technical users.

Learn more about web upload

Native HTTP Strict Transport Security (HSTS) support

The HTTP Strict Transport Security (HSTS) policy enforces the use of the secure HTTPS protocol when accessing the server. When the policy is enabled on a server, all HSTS-capable clients will contact the server only through a secure connection (HTTPS). Thus, this policy helps to protect against man-in-the-middle attacks and does not allow users to ignore certificate warnings.

Although all modern web browsers support HSTS, current Subversion client versions do not. If you enable this option, it will be recognized by web browsers but ignored by clients such as svn.exe and TortoiseSVN. However, enabling HSTS does not have any negative effects on Subversion clients.

Learn more about HSTS

Generating a new private key for TLS/SSL

A new private key can be generated when creating a new Certificate Signing Request (CSR). This feature can help users whose Certificate Authority (CA) requires CSR to be always generated with a new private key.

Generating a new private key is also supported when creating a new self-signed certificate or obtaining a certificate from Active Directory Certificate Services (AD CS).

Server-wide access rules for Subversion authentication

VisualSVN Server 5.1 supports server-wide (global) access rules for the Subversion authentication mode. These access rules can be configured on the server-wide level and propagate to all repositories hosted on the server, therefore simplifying administration.

Server-wide access rules for Subversion authentication were removed in VisualSVN Server 2.6, and are reintroduced in version 5.1. This also simplifies upgrade procedures for those upgrading from very old server installations.

More enhancements

Other notable improvements in this version are listed below:

• New Get-SvnRepositoryItemLock and Remove-SvnRepositoryItemLock PowerShell cmdlets to list and remove locks from a repository.
• New installations now enable 'Implicit list folder permission' in the default repository security settings.
• Configure access to the certificate directory using Service SID instead of the Service Logon account.
• Configure access to the repositories root directory using Service SID instead of the Service Logon account.

View detailed changelog

Upgrading to new version

Upgrade to VisualSVN Server 5.1 is recommended for all users. Please read the KB204: Upgrading to VisualSVN Server 5.1 article before upgrading.

The upgrade is free for all customers who have an active maintenance subscription for Enterprise or Essential licenses. The upgrade is also free for all customers who use VisualSVN Server under the Community license.

The Apache HTTP Server 2.4.54 patch release addresses the CVE-2022-31813 and CVE-2022-26377 vulnerabilities found in the mod_proxy and mod_proxy_ajp Apache modules, respectively. Both affected modules are shipped with VisualSVN Server, but they are not loaded or enabled by default. Therefore, these vulnerabilities do not affect VisualSVN Server installations unless the modules were manually enabled by an administrator.

Other vulnerabilities fixed in Apache HTTP Server 2.4.54 and OpenSSL 1.1.1q do not affect up-to-date VisualSVN Server installations. Nevertheless, upgrading to the new builds is recommended for all users.

Update for VisualSVN Server

Get the latest version of VisualSVN Server from the official download page. For a detailed list of changes, see the VisualSVN Server 5.0.3 changelog.

Choose an appropriate maintenance build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.3.10 if you have version 4.3.x installed.
• VisualSVN Server 4.2.13 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 5.0.x if you are using any version family older than 4.2.x. Read the article KB174: Upgrading to VisualSVN Server 5.0 before upgrading.

The CVE-2022-1292 vulnerability does not affect up-to-date versions of VisualSVN products. Although the vulnerability does not affect up-to-date VisualSVN products, it is recommended that all users upgrade to the latest builds.

Update for VisualSVN Server

Get the latest version of VisualSVN Server from the official download page. For a detailed list of changes, see the VisualSVN Server 5.0.2 changelog.

Choose an appropriate maintenance build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.3.9 if you have version 4.3.x installed.
• VisualSVN Server 4.2.12 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 5.0.x if you are using any version family older than 4.2.x. Read the article KB174: Upgrading to VisualSVN Server 5.0 before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.0.4.
• If you use Visual Studio 2019, update to VisualSVN 7.3.7.
• If you use Visual Studio 2017, update to VisualSVN 6.7.6.
• If you use Visual Studio 2015 or older, update to VisualSVN 5.6.6.

Get the latest version of VisualSVN from the official download page.

The update to Apache Subversion 1.14.2 and zlib 1.2.12 fixes several vulnerabilities, but none of them affect up-to-date VisualSVN Server installations or the VisualSVN plug-in. Although the vulnerabilities do not affect up-to-date VisualSVN products, it is recommended that all users upgrade to the latest builds.

Update for VisualSVN Server

Get the latest version of VisualSVN Server from the official download page. For a detailed list of changes, see the VisualSVN Server 5.0.1 changelog.

Choose an appropriate maintenance build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.3.8 if you have version 4.3.x installed.
• VisualSVN Server 4.2.10 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 5.0.x if you are using any version family older than 4.2.x. Read the article KB174: Upgrading to VisualSVN Server 5.0 before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.0.3.
• If you use Visual Studio 2019, update to VisualSVN 7.3.6.
• If you use Visual Studio 2017, update to VisualSVN 6.7.5.
• If you use Visual Studio 2015 or older, update to VisualSVN 5.6.5.

Get the latest version of VisualSVN from the official download page.

• Full-text search for repository content and history
• Email notifications for background jobs
• Implicit list folder permission for parents of readable paths
• Scheduling incremental backups multiple times a day
• Strong password policy for Subversion authentication

There are many other significant improvements related to various VisualSVN Server features, some of which are listed below. For the complete list of changes, see the VisualSVN Server 5.0.0 changelog.

The upgrade to VisualSVN Server 5.0 is recommended for all users. We strongly advise reading the article KB174: Upgrading to VisualSVN Server 5.0 before beginning the upgrade.

Download VisualSVN Server 5.0 from the main download page.

Full-text search for repository content and history

One of the big changes in version 5.0 is the new full-text search feature. We've built a custom search engine specifically for Subversion repositories, considering their distinctive traits such as path-based authorization, arbitrary repository layouts and file sizes.

The new search engine indexes every revision of the data stored in your repositories and makes it searchable through the web interface. Users can search for content, filename and log message matches in any folder they have access to, and the results are filtered according to the authorization settings.

Search is not limited to the HEAD revision, but instead every single revision is searchable — whether it is the most recent revision or a revision that was committed several years ago.

The search engine supports a wide set of capabilities, including:

• Exact expression matches, such as "hello world".
• Complex expressions, such as filename:*.h content:(for example).
• Metadata queries, such as author:svn-role.
• Specialized handling of camelCase, under_score and numeric identifiers.

The new search feature is available for all users with Enterprise or Essential licenses.

Learn more about full-text search

Email notifications for background jobs

VisualSVN Server 5.0 now supports email notifications for background jobs, allowing for easier monitoring of their status and activity. Background job notifications are sent after a job has finished running, notifying the administrator of the job run status.

Learn more about job notifications

Implicit list folder permission for parents of readable paths

We extended the path-based authorization system for more convenient permission management and better user experience.

Imagine that a user has read access to /repos/project/trunk. Previously, this would mean that:

• The user cannot browse to this location starting from the server root.
• The user cannot access it unless he knows the repository name and the exact path.
• The user cannot see the repository in the repository list.

To remove these limitations, VisualSVN Server 5.0 adds a per-repository option that automatically grants list folder permission to parents of paths readable by a user.

This option allows users to browse to any location they have read access to, starting from the server root. The actual read access levels are not changed.

We recommend enabling the new option for all existing and new repositories. For convenience, its state for new repositories can be changed in the server configuration.

Learn more about new implicit permission

Scheduling incremental backups multiple times a day

With a series of improvements for the Backup and Restore feature, VisualSVN Server now offers a near-continuous data protection solution.

Starting from version 5.0, new and existing incremental backup jobs can be configured to run multiple times a day, as frequent as every 15 minutes.

Learn more about backup and restore

Strong password policy for Subversion authentication

To improve security of the environments that rely on user passwords, VisualSVN Server 5.0 allows enforcing a strong password policy for the Subversion authentication mode. The strong password policy is also enabled by default for new installations.

An administrator can configure the password policy by specifying the desired minimum password length and password complexity.

Learn more about password policy

More enhancements

A few other notable improvements in this version are listed below:

• Various enhancements to the web interface, such as support for svn:externals or highlighting links and revision numbers in the log messages.
• New background job to cleanup uncommitted transactions.
• Support for renaming files and folders in VisualSVN Server Manager.
• Essential license now supports the Access and Operational logging feature.
• New check-pathnames pre-commit hook.
• Improvements to the commit-notification post-commit hook.

View detailed changelog

Web interface no longer supports Internet Explorer

Starting from version 5.0, the VisualSVN Server web interface does not support Internet Explorer. If you use Internet Explorer to access the web interface, you are required to upgrade to Microsoft Edge or switch to another supported browser.

Note that the Internet Explorer 11 desktop application will go out of support (for certain operating systems) starting June 15, 2022. And Microsoft encourages customers to move to Microsoft Edge with Internet Explorer (IE) mode.

This change only affects the client repository web interface. It does not affect any server administration capabilities or the VisualSVN Server Manager console.

Deprecated TLS 1.0 and TLS 1.1 protocols are now at the Legacy level

TLS 1.0 and TLS 1.1 protocols have been officially deprecated by RFC 8996. VisualSVN Server 5.0 no longer enables these protocols at the default Intermediate TLS/SSL compatibility level, and only enables them at the Legacy TLS/SSL compatibility level.

During an upgrade of the existing server, the installer will offer an option to change the TLS/SSL compatibility level setting. If you have outdated clients that do not support TLS 1.2, please consider switching to the Legacy level until those clients can be updated. Pay attention to the following clients:

• TortoiseSVN version 1.7.8 or older.
• Subversion command line client version 1.8.x or older.
• All clients based on Java 7 or older.

Learn more about TLS 1.0 and TLS 1.1 deprecation

Other compatibility changes

Please consider the list of other compatibility changes in VisualSVN Server 5.0:

• Windows Server 2008 R2 and Windows Server 2012 are no longer supported. The minimum supported operating system is Windows Server 2012 R2.
• The outdated SSL 3.0 protocol is no longer supported.
• Remote Server Administration of VisualSVN Server 4.1.x and older versions is no longer supported.

Known issues

Please consider the list of known issues before upgrading to VisualSVN Server 5.0.

Upgrading to new version

The upgrade to VisualSVN Server 5.0 is recommended for all users. Please read the KB174: Upgrading to VisualSVN Server 5.0 before upgrading. The upgrade is free for all customers who have an active maintenance subscription for Enterprise or Essential licenses. The upgrade is also free for all customers who use VisualSVN Server under the Community license.

This update fixes a number of security vulnerabilities, some of which may affect both VisualSVN and VisualSVN Server in certain configurations. Therefore, updating to the new builds is recommended for all users.

Update for VisualSVN Server

Get the latest version of VisualSVN Server from the official download page. For the list of changes, see the VisualSVN Server 4.3.7 changelog.

Choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.9 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.3.7 if you are using any version family older than 4.2.x. Please read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2022, update to VisualSVN 8.0.2.
• If you use Visual Studio 2019, update to VisualSVN 7.3.5.
• If you use Visual Studio 2017, update to VisualSVN 6.7.4.
• If you use Visual Studio 2015 or older, update to VisualSVN 5.6.4. Note that VisualSVN 5.6.4 is still using Expat XML parser 2.2.10. Update to Expat XML parser 2.4.x is expected in future releases.

Get the latest version of VisualSVN from the official download page.

For the complete list of changes, see the VisualSVN Server 4.3.6 changelog.

This update fixes several security vulnerabilities:

• The update to Apache HTTP Server 2.4.52 fixes two vulnerabilities: CVE-2021-44224 and CVE-2021-44790. Default VisualSVN Server installations are not affected by these vulnerabilities.
• The update to Expat XML parser 2.4.3 cumulatively fixes nine vulnerabilities: CVE-2013-0340, CVE-2021-45960, CVE-2021-46143, CVE-2022-22822, CVE-2022-22823, CVE-2022-22824, CVE-2022-22825, CVE-2022-22826, and CVE-2022-22827. Up-to-date VisualSVN Server installations are potentially affected by some of these vulnerabilities, so updating to the new builds is recommended for all users.

You can get the latest VisualSVN Server version on the official download page.

Maintenance releases

Choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.8 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them.

It is strongly recommended to upgrade to VisualSVN Server 4.3.x if you are using any version family older than 4.2.x. Read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Vulnerability information

CVE-2021-44228 is a critical remote code execution vulnerability in the Apache Log4j Java library. Information about the vulnerability has been publicly disclosed on December 9, 2021. At the time of writing, the vulnerability is known to be actively exploited in the wild.

VisualSVN Server is not affected

VisualSVN Server is NOT AFFECTED by the CVE-2021-44228 (Log4Shell) vulnerability.

VisualSVN Server and its components are not based on Java, and they do not depend on the vulnerable Apache Log4j library.

Although VisualSVN Server itself is not affected, it is recommended to check if your Subversion repositories have custom or third-party hooks that use Java and the vulnerable Apache Log4j library. If so, the risks are still limited because triggering a hook script requires access permissions to the corresponding repository. However, in this case it is strongly recommended to follow the official guidelines on mitigating the vulnerability.

VisualSVN for Visual Studio is not affected

VisualSVN for Visual Studio is NOT AFFECTED by the CVE-2021-44228 (Log4Shell) vulnerability.

VisualSVN for Visual Studio and its components are not based on Java, and they do not depend on the vulnerable Apache Log4j library.

Compared to the previous versions, Visual Studio 2022 is a 64-bit application, and the update includes a hotfix for one related error that could occur with certain project types. Please see the details and the complete list of changes in the VisualSVN 8.0.1 changelog.

The update is recommended for all users of VisualSVN for Visual Studio 2022.

You can get the latest version of VisualSVN on the official download page.

Upgrading to VisualSVN 8.0 is necessary if you are switching to Visual Studio 2022. Professional and Site licenses issued before June 17th, 2021 require purchasing an upgrade for VisualSVN 8.0. The upgrade to VisualSVN 8.0 is free if you use VisualSVN under the Community license.

VisualSVN 8.0 can be installed and updated directly in Visual Studio (Extensions | Manage Extensions). You can also download the latest VisualSVN 8.0 build from the official download page.

You can purchase an upgrade to VisualSVN 8.0 using the online purchase form.

Support for Visual Studio 2022

VisualSVN 8.0 enables full integration with Visual Studio 2022, which is now a 64-bit application.

Visual Studio 2022 is the first 64-bit version of Visual Studio that allows you to work with the most complex solutions without considering memory constraints. To allow for a seamless integration, all internal components of VisualSVN 8.0 have been migrated to the 64-bit architecture as well.

Personal and Corporate licenses reintroduced

Starting from October 2021, the Professional license that has been available in recent years is replaced by the reintroduced Personal and Corporate licenses:

• Personal license is intended for use by individuals and is licensed to a specific named person.
• Corporate license is intended for use by companies and organizations and is licensed per developer.

The Professional license is now obsolete and will be upgraded to one of the new license types when ordering an upgrade to VisualSVN 8.0. However, all Professional licenses issued on or after June 17th, 2021 are eligible for a free upgrade to VisualSVN 8.0 without requiring to change the license key.

There are no changes to the free Community license and to the Site license for large organizations. Please, see the VisualSVN Licensing page for more information.

Upgrading existing licenses to VisualSVN 8.0

All VisualSVN 7.x licenses issued on or after June 17th, 2021 are eligible for a free upgrade to VisualSVN 8.0 without requiring to change the license key. The upgrade to VisualSVN 8.0 is also free if you use VisualSVN under the Community license.

Commercial licenses issued before June 17th, 2021 require an upgrade purchase for VisualSVN 8.0. In connection with the reintroduced Personal and Corporate license types, there is a special procedure for upgrading existing licenses to version 8.0.

Regular upgrade prices are as follows:

• Upgrade to Personal license: $29 (for individual use only).
• Upgrade to Corporate license: $69 per developer.
• Site license upgrade: $1950 per site.

Also, please note that until November 21, an upgrade to Corporate license is available for $49 per developer.

You can purchase an upgrade to VisualSVN 8.0 using the online purchase form.

VisualSVN Server is not affected by the critical CVE-2021-41773 and CVE-2021-42013 vulnerabilities that were recently found in the Apache HTTP Server. Default VisualSVN Server installations also are not affected by the other vulnerabilities found in the Apache HTTP Server. However, both VisualSVN and VisualSVN Server may be affected by the CVE-2021-3711 and CVE-2021-3712 vulnerabilities found in OpenSSL, so updating to the new builds is highly recommended for all users.

Update for VisualSVN Server

Get the latest version of VisualSVN Server on the official download page. For the list of changes, see the VisualSVN Server 4.3.5 changelog.

Choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.7 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.3.5 if you are using any version family older than 4.2.x. Please read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2019, update to VisualSVN 7.3.4.
• If you use Visual Studio 2017, update to VisualSVN 6.7.3.
• If you use Visual Studio 2015 or older, update to VisualSVN 5.6.3.

Get the latest version of VisualSVN on the official download page.

Get the latest version of VisualSVN Server on the official download page. For the list of changes, see the VisualSVN Server 4.3.4 changelog.

Maintenance release

Choose an appropriate maintenance patch release if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.6 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported, and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.3.4 if you are using any version family older than 4.2.x. Please read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Up-to-date VisualSVN Server installations are affected only by the CVE-2021-3449 vulnerability that allows a remote attacker to cause a denial of service. Exploiting this vulnerability does not require an attacker to be authenticated on a target server, so upgrading to VisualSVN Server 4.3.3 is highly recommended for all users.

Up-to-date VisualSVN installations are not affected by any of the aforementioned vulnerabilities. Nevertheless, upgrading to the new builds is recommended for all users.

Upgrade for VisualSVN Server

Get the latest version of VisualSVN Server on the official download page. For the list of changes, see the VisualSVN Server 4.3.3 changelog.

Choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.5 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.3.3 if you are using any version family older than 4.2.x. Please read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Upgrade for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2019, upgrade to VisualSVN 7.3.3.
• If you use Visual Studio 2017, upgrade to VisualSVN 6.7.2.
• If you use Visual Studio 2015 or older, upgrade to VisualSVN 5.6.2.

Get the latest version of VisualSVN on the official download page.

The update is recommended for all users of VisualSVN for Visual Studio 2019.

You can get the latest version of VisualSVN on the official download page.

Update to Apache Subversion 1.14.1 contains a fix for CVE-2020-17525 which is rated as a high severity server-side vulnerability. However, up-to-date VisualSVN Server installations are not affected as the mod_authz_visualsvn module used in the server is not vulnerable to this issue. Update to OpenSSL 1.1.1j contains cumulative fixes for three CVEs, but none of them affects up-to-date VisualSVN or VisualSVN Server installations.

Nevertheless, upgrading to the new builds is recommended for all users.

Upgrade for VisualSVN Server

Get the latest version of VisualSVN Server on the official download page. For the detailed list of changes, see the VisualSVN Server 4.3.2 changelog.

Choose an appropriate maintenance build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.4 if you have version 4.2.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.3.x if you are using any version family older than 4.2.x. Read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Upgrade for VisualSVN (a plug-in for Visual Studio)

Select an appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2019, upgrade to VisualSVN 7.3.1.
• If you use Visual Studio 2017, upgrade to VisualSVN 6.7.1.
• If you use Visual Studio 2015 or older, upgrade to VisualSVN 5.6.1.

Get the latest version of VisualSVN on the official download page.

Download the latest VisualSVN Server builds at the main download page.

The whole product family of VisualSVN Server continues to be actively developed. We continue to provide updates and support for VisualSVN Server 4.3.x which is the most recent version family and is linked with up-to-date OpenSSL 1.1.1, Apache HTTP Server 2.4.x, and Apache Subversion 1.14.x Long-Term Support release. We also continue to provide maintenance updates and support for the VisualSVN Server 4.2.x version family which is linked with Apache Subversion 1.10.x.

What is more, we are working on substantial improvements and exciting new features that are going to be introduced in the next updates.

Upgrade and compatibility concerns

Upgrade to VisualSVN Server 4.3.x is recommended for all users. The upgrade process is straightforward, but it is highly recommended to read the article KB167: Upgrading to VisualSVN Server 4.3 beforehand.

For the complete list of changes, see the VisualSVN Server 4.3.1 changelog.

The Apache HTTP Server 2.4.46 release fixes the CVE-2020-9490, CVE-2020-11993 and CVE-2020-11984 vulnerabilities, but none of them affect up-to-date VisualSVN Server installations. The vulnerabilities were found in the mod_http2 and mod_proxy_uwsgi Apache modules which are not used in VisualSVN Server. Nevertheless, the upgrade to newer VisualSVN Server builds is recommended for all users.

You can get the latest VisualSVN Server version on the official download page.

Maintenance releases

Choose an appropriate maintenance patch update if you do not want to perform a significant upgrade right now:

• VisualSVN Server 4.2.3 if you have version 4.2.x installed.
• VisualSVN Server 4.1.5 if you have version 4.1.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.3.x if you are using any version family older than 4.1.x. Read the KB167: Upgrading to VisualSVN Server 4.3 article before upgrading.

Upgrade to the latest VisualSVN Server and VisualSVN plug-in is recommended for all users:

• Download VisualSVN Server 4.3.
• Download VisualSVN 7.3 for Visual Studio 2019.
• Download VisualSVN 6.7 for Visual Studio 2017.
• Download VisualSVN 5.6 for Visual Studio 2015 and older.

What’s new in Apache Subversion 1.14

Apache Subversion 1.14 is the latest LTS (Long-Term Support) release that includes all improvements, features, and bug fixes since the previous 1.10 LTS release. It also includes changes not present in any earlier releases. For the complete list of changes, please refer to the Apache Subversion 1.14 Release Notes.

Subversion LTS releases are made available every 2 years and get a 4-year support period. See the details on the Apache Subversion Roadmap page.

Upgrade for VisualSVN Server

VisualSVN Server 4.3 brings an update to Apache Subversion 1.14 and includes several bug fixes. Note that it is backward compatible with all older Subversion clients. For more details and the VisualSVN Server 4.3 client compatibility matrix, see the VisualSVN Server 4.3 Release Notes.

Upgrade to VisualSVN Server 4.3 is recommended for all users. The upgrade is easy and straightforward. For further details, please read the KB167: Upgrading to VisualSVN Server 4.3 article.

You may download VisualSVN Server 4.3 at the main download page.

Upgrade for VisualSVN (a plug-in for Visual Studio)

VisualSVN plug-in version depends on your Visual Studio version:

• Users of Visual Studio 2019 should upgrade to VisualSVN 7.3.
• Users of Visual Studio 2017 should upgrade to VisualSVN 6.7.
• Users of Visual Studio 2015 or older should upgrade to VisualSVN 5.6.

You may download an appropriate VisualSVN version at the official download page.

The upgrade is straightforward and does not require upgrading your working copies.

Upgrade for TortoiseSVN

Please be aware that TortoiseSVN 1.14.0 does not always install properly when upgrading from TortoiseSVN 1.13.x The problem can be fixed by repairing the TortoiseSVN installation. This problem is specific to TortoiseSVN 1.14.0 and will be fixed in the next 1.14.1 version.

TortoiseSVN 1.13.x users may choose to upgrade VisualSVN now, and upgrade TortoiseSVN once the version 1.14.1 is released. Both TortoiseSVN 1.13.x and TortoiseSVN 1.14.x are fully compatible with the upgraded VisualSVN plug-in and use the same working copy format.

Download the latest VisualSVN Server builds at the main download page.

The whole product family of VisualSVN Server continues to be actively developed. We continue to provide updates and support for VisualSVN Server 4.2.x which is the most recent version family and is linked with up-to-date OpenSSL 1.1.1, Apache HTTP Server 2.4.x, and Apache Subversion 1.10.x Long-Term Support release. We also continue to provide maintenance updates and support for the VisualSVN Server 4.1.x version family.

What is more, we are working on substantial improvements and exciting new features that are going to be introduced in the next updates.

Upgrade and compatibility concerns

Upgrade to VisualSVN Server 4.2.x is recommended for all users. The upgrade process is straightforward, but it is highly recommended to read the article KB161: Upgrading to VisualSVN Server 4.2 beforehand.

The VisualSVN Server 4.2.2 is available on the official download page. For the full list of changes, see the VisualSVN Server 4.2.2 changelog.

Note that the CVE-2020-1967 vulnerability does not affect the VisualSVN Server 4.0.x family. That is because the previous build of this version family gets updated from OpenSSL 1.1.1c, which is not vulnerable to the CVE-2020-1967.

New builds also include the update to Apache HTTP Server 2.4.43 which fixes two CVEs: CVE-2020-1934 and CVE-2020-1927. Up-to-date VisualSVN Server installations are potentially affected by the CVE-2020-1927, which is a medium severity vulnerability.

Upgrade is also recommended for users of earlier VisualSVN Server version families. Please, read VisualSVN Server 4.2 Release Notes to find out what's new in the latest release. For detailed upgrade instructions please see the KB161: Upgrading to VisualSVN Server 4.2 knowledge base article.

If you are not ready to proceed with a significant upgrade, choose an appropriate patch build:

• VisualSVN Server 4.1.4 if you have version 4.1.x installed.
• VisualSVN Server 4.0.5 if you have version 4.0.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.2.x if you are using any version family older than 4.0.x. Read the KB161: Upgrading to VisualSVN Server 4.2 article before upgrade.

For the detailed list of changes, see the VisualSVN Server 4.2.1 changelog.

The upgrade to the VisualSVN Server 4.2.1 is recommended for all VisualSVN Server users. You can get the latest version of VisualSVN Server on the official download page.

• Finding files by name in the web interface.
• Viewing the background jobs history.
• Managing local Subversion users, groups and their permissions with PowerShell.

For the complete list of changes, see the VisualSVN Server 4.2.0 changelog.

Upgrade to VisualSVN Server 4.2 is recommended for all users. Upgrade is easy and straightforward, but we strongly advise reading the KB161: Upgrading to VisualSVN Server 4.2 article beforehand (especially if you are upgrading from VisualSVN Server 3.9 or older versions).

Download VisualSVN Server 4.2 from the main download page.

Finding files by name in the web interface

VisualSVN Server 4.2 introduces finding files and folders in the web interface. Web interface supports finding files in the entire repository as well as in subfolders, including branches or tags. Furthermore, there is an option for finding files at a specific repository revision. A search query can include the asterisk (*) and question-mark (?) wildcard characters.

Web interface finds files and folders based on user access rights, keeping your data secure from unauthorized use. If no access is allowed, files will not be shown in the search output and cannot be retrieved in any other way.

Try out the new feature on one of the demo server’s repositories.

Viewing the background jobs history

VisualSVN Server 4.2 adds Job History to the VisualSVN Server Manager console that shows a quick summary on a particular job. The detailed information on each particular job run instance is available with the Show Details option. For instance, an in-depth information on a Verify Repository job may help finding out in which of repositories a corruption has been found.

Job History shows all the runs that are currently present in the VisualSVN Server Background Jobs event log.

Managing local Subversion users, groups and their permissions with PowerShell

VisualSVN Server 4.2 adds new PowerShell cmdlets for managing local Subversion user and group accounts and their access rules.

The new capabilities are as follows:

• Create, remove and manage local Subversion user accounts.
• Create, remove and manage Subversion group accounts and its members.
• Manage access rights for Subversion authentication.

Find the list of new cmdlets in the VisualSVN Server 4.2.0 changelog. Or see the KB88: VisualSVN Server PowerShell Cmdlet Reference article for the updated list of all the cmdlets available.

Other changes

VisualSVN Server 4.2 also has several other notable changes:

• New Multi-Processing Module (MPM) dynamically adapting to workload. New module improves performance by using a dynamically-sized thread pool that scales with the number of connected clients and the available server resources.
• Do not backup rep-cache.db. Recreate the rep-cache file when restoring a repository from backup instead. As a consequence, incremental backups for large repositories are indeed small.
• Disallow creating user and group accounts with the same names but with different letter case. Existing users with identical names, if any, will not be affected.

For the complete list of changes, see the VisualSVN Server 4.2.0 changelog.

Upgrade and compatibility concerns

Upgrade to VisualSVN Server 4.2 is recommended for all users. Please read the KB161: Upgrading to VisualSVN Server 4.2 article before upgrading.

The upgrade is free for all customers who have active maintenance subscription for Enterprise or Essential licenses. The upgrade is also free for all customers who use VisualSVN Server under the Community license.

Upgrade to the latest versions of VisualSVN plug-in is recommended for all users. Latest VisualSVN builds are available on the official download page.

What’s new in Apache Subversion 1.13

Apache Subversion 1.13 is the latest regular (non-LTS) release that includes several improvements and bug fixes. For the complete list of changes, please refer to the Apache Subversion 1.13 Release Notes.

Non-LTS releases are made available every 6 months and designated to deliver new features and enhancements in a timely fashion. See the details on the Apache Subversion Roadmap page.

Upgrade for VisualSVN (a plug-in for Visual Studio)

Select the appropriate VisualSVN plug-in version with respect to your Visual Studio version:

• If you use Visual Studio 2019, upgrade to VisualSVN 7.2.
• If you use Visual Studio 2017, upgrade to VisualSVN 6.6.
• If you use Visual Studio 2015 or older, upgrade to VisualSVN 5.5.

The upgrade procedure is straightforward and does not require upgrading your working copies. To fully benefit from the improvements made in Apache Subversion 1.13, consider an upgrade to the latest TortoiseSVN version. Installation files are available on the download page.

VisualSVN Server compatibility

Clients based on Subversion 1.13 are fully compatible with VisualSVN Server 4.1 that is built on Subversion 1.10.

We draw your attention that Subversion 1.10 is the latest available Long-Term Support release. Given that no significant server-side or protocol-related changes have been introduced in subsequent regular Subversion 1.11, 1.12, 1.13 releases, VisualSVN Server 4.1 functionality is entirely consistent with any of those non-LTS releases.

Download the latest VisualSVN Server builds at the main download page.

The whole product family of VisualSVN Server continues to be actively developed. We continue to provide updates and support for VisualSVN Server 4.1.x which is the most recent version family and is linked with up-to-date OpenSSL 1.1.1, Apache HTTP Server 2.4.x, and Apache Subversion 1.10.x Long-Term Support release. We also continue to provide maintenance updates and support for the VisualSVN Server 4.0.x version family.

What is more, we are working on substantial improvements and exciting new features that are going to be introduced in the next updates.

Upgrade and compatibility concerns

It is highly recommended to read the article KB152: Upgrading to VisualSVN Server 4.1 before upgrading.

Starting from version 4.0, Standard and Enterprise Editions are replaced with new Community, Essential, and Enterprise licenses. During the upgrade to version 4.1, your server will automatically switch to the new licensing model. If you are upgrading from Standard Edition, in most cases, it will be automatically replaced by the free Community license. However, if you use Windows Authentication or if there are more than 15 Subversion user accounts, you will need to apply a sufficient Essential or Enterprise license key or start the 45 days evaluation period. Read the article KB147: How the licensing model changes in VisualSVN Server 4.0 for more information.

Starting from VisualSVN Server 4.0, the repository web interface no longer supports Internet Explorer 10. You need to upgrade to Internet Explorer 11 or use another browser that is supported by the repository web interface. Please read the article KB151: Browsers supported by VisualSVN Server Web Interface for more information.

• Pack Repository background job. This new scheduled background job allows to pack repositories on a regular basis. Packing reduces the number of files on disk and therefore reduces storage and maintenance overhead. For further information and configuration instructions please consider the article KB156: Getting started with Pack Repository Jobs.
• Side-by-side diff for images in the web interface. New side-by-side diff for images in the web interface makes it possible to preview image differences in the web browser.
• TLS 1.3 protocol support. TLS 1.3 is the most recent version of the HTTP encryption protocol that provides enhanced security, performance and privacy compared to the previous versions. VisualSVN Server now fully supports this version of the protocol and enables it by default. Note that TLS 1.3 will be actually used only if it is supported by the client.
• New Enterprise Multinode license. The new license type is suitable for multisite VisualSVN Server deployments. If you use the Multisite Repository Replication feature and have several VisualSVN Server instances connected within a single distributed VDFS cluster, you can now purchase a single Enterprise Multinode license and use it on all these server instances. This option is cost-effective, and it also simplifies deployment and licensing-related maintenance tasks.

For the complete list of changes, see the VisualSVN Server 4.1.0 changelog.

Upgrade to VisualSVN Server 4.1 is recommended for all users. Upgrade is easy and straightforward, but we strongly advise reading the KB152: Upgrading to VisualSVN Server 4.1 article beforehand (especially if you are upgrading from VisualSVN Server 3.9 or older versions).

Download VisualSVN Server 4.1 from the main download page.

Updates to PowerShell Cmdlets

The new release adds a capability to deploy and manage the Repository Management Delegation feature via PowerShell and deprecates two existing cmdlets.

• It is now possible to deploy and manage the Repository Management Delegation feature using the Get-SvnRepository, Set-SvnRepository, Get-SvnServerConfiguration, and Set-SvnServerConfiguration cmdlets.
• Get-SvnRepositoryReplication and Set-SvnRepositoryReplication cmdlets have been deprecated. Their functionality has been merged into Get-SvnRepository and Set-SvnRepository cmdlets.

For the complete list of PowerShell cmdlets available in VisualSVN Server 4.1, see the KB88: VisualSVN Server PowerShell Cmdlet Reference.

Upgrade and compatibility concerns

Upgrade to VisualSVN Server 4.1 is recommended for all users. Please read the KB152: Upgrading to VisualSVN Server 4.1 article before upgrading.

The upgrade is free for all customers who have active maintenance subscription for Enterprise or Essential licenses. The upgrade is also free for all customers who use VisualSVN Server under the Community license.

Please upgrade to VisualSVN Server 4.0.4 that is available for download at the main download page. For the complete list of changes, see the VisualSVN Server 4.0.4 changelog.

Up-to-date VisualSVN Server installations are potentially affected by the CVE-2019-10098 vulnerability. This is a low-risk vulnerability and it has no security impact in VisualSVN Server. Nevertheless, the upgrade to newer VisualSVN Server builds is recommended for all users.

Note that the Apache HTTP Server 2.4.41 patch release also addresses the CVE-2019-10092 and CVE-2019-10097 vulnerabilities found in the mod_proxy and mod_remoteip Apache modules, respectively. Both affected modules are shipped with VisualSVN Server, but they are not loaded or enabled by default. Therefore, these vulnerabilities do not affect VisualSVN Server installations unless the modules were manually enabled by an administrator.

Maintenance releases

Choose an appropriate maintenance patch update if you do not want to perform a significant upgrade right now:

• VisualSVN Server 3.9.7 if you have version 3.9.x installed.
• VisualSVN Server 3.8.9 if you have version 3.8.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.0.x if you are using any version family older than 3.8.x. Read the KB149: Upgrading to VisualSVN Server 4.0 article before upgrading.

Download the latest VisualSVN Server builds at the main download page.

The whole product family of VisualSVN Server continues to be actively developed. We continue to provide maintenance updates and support for VisualSVN Server 4.0.x which is the most recent version family and is linked with up-to-date OpenSSL 1.1.1, Apache HTTP Server 2.4.x and Apache Subversion 1.10.x. We also provide support and release updates for VisualSVN Server 3.9.x that is linked with OpenSSL 1.0.2.

What is more, we are working on substantial improvements and exciting new features that are going to be introduced in the next updates.

Upgrade and compatibility concerns

It is highly recommended to read the article KB149: Upgrading to VisualSVN Server 4.0 before upgrading.

Starting from version 4.0, Standard and Enterprise Editions are replaced with new Community, Essential and Enterprise licenses. During the upgrade to version 4.0, your server will automatically switch to the new licensing model. If you are upgrading from Standard Edition, in most cases it will be automatically replaced by the free Community license. However, if you use Windows Authentication or if there are more than 15 Subversion user accounts, you will need to apply a sufficient Essential or Enterprise license key or start the 45 days evaluation period. Read the article KB147: How the licensing model changes in VisualSVN Server 4.0 for more information.

Starting from VisualSVN Server 4.0, the repository web interface no longer supports Internet Explorer 10. You need to upgrade to Internet Explorer 11 or use another supported browser with the repository web interface. Read the article KB151: Browsers supported by VisualSVN Server Web Interface for more information.

Support for multiple working copies within a single solution was first introduced in VisualSVN 7.1 for Visual Studio 2019. This new functionality is now also available to Visual Studio 2017 users. See the changelog for a complete list of changes.

You can download the latest VisualSVN 6.5 build from the official download page.

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.

Upgrading existing licenses to VisualSVN 6.5

All VisualSVN 6.x licenses are eligible for a free upgrade to VisualSVN 6.5. VisualSVN 5.x licenses issued on or after March 30th, 2016 are eligible for a free upgrade, too. The upgrade to VisualSVN 6.5 is also free if you use VisualSVN under the Community license.

If you have older VisualSVN license keys you can purchase an upgrade to VisualSVN 7.x license that is also valid for VisualSVN 6.x versions. You can purchase an upgrade to VisualSVN 7.x using the online purchase form.

Apache Subversion 1.12.2 patch release addresses the CVE-2018-11782 and CVE-2019-0203 DoS vulnerabilities, which do not affect VisualSVN products. However, up-to-date VisualSVN Server installations are affected by the CVE-2018-20843 (remotely triggerable DoS, requires read access to the target server) that was addressed in the Expat XML parser 2.2.7 patch release. We consider the risks to be moderate, because VisualSVN Server does not allow anonymous read access. Therefore, upgrading to the new VisualSVN Server builds is highly recommended for all users.

Update for VisualSVN Server

Users of VisualSVN Server should update to VisualSVN Server 4.0.3. For the list of changes, see the VisualSVN Server 4.0.3 changelog.

It is also recommended to upgrade to version 4.0.3 if you are using an earlier version family of VisualSVN Server. Please, read VisualSVN Server 4.0 Release Notes to find out what's new in the latest release. For detailed upgrade instructions please consider the KB149: Upgrading to VisualSVN Server 4.0 knowledge base article.

Choose an appropriate patch build if you do not want to perform a significant upgrade right now:

• VisualSVN Server 3.9.6 if you have version 3.9.x installed.
• VisualSVN Server 3.8.8 if you have version 3.8.x installed.

Other version families of VisualSVN Server are not supported and maintenance updates are not available for them. It is strongly recommended to upgrade to VisualSVN Server 4.0.x if you are using any version family older than 3.8.x. Read the KB149: Upgrading to VisualSVN Server 4.0 article before upgrading.

Update for VisualSVN (a plug-in for Visual Studio)

You can download the latest VisualSVN 7.1.2 (for Visual Studio 2019), 6.4.1 (for Visual Studio 2017) and 5.4.1 (for Visual Studio 2015 and older) from the official download page.

Please note that VisualSVN 6.x or older users who do not have a valid 7.x license may need to upgrade the licenses. The upgrade is free if you are using VisualSVN under the Community License. For further details, please check the VisualSVN plug-in Licensing page.

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.

VisualSVN Server versions 4.0.0 and 4.0.1 have a minor bug that could affect how Windows users are counted towards the limit of the new licenses. More specifically, Windows users with no repository access could have been incorrectly counted as active after viewing the repositories list. This issue is resolved in the VisualSVN Server 4.0.2 patch update.

See the changelog for the complete list of changes.

The update is recommended for all users of VisualSVN Server 4.0.x. You can get the latest version of VisualSVN from the official download page.

For the detailed list of changes, see the VisualSVN Server 4.0.1 changelog.

OpenSSL 1.1.1c patch release addresses the CVE-2019-1543 vulnerability. Non-customized VisualSVN Server installations are not affected by this vulnerability, because all predefined TLS/SSL compatibility levels do not allow using the affected ChaCha20-Poly1305 cipher. Nevertheless, we recommend that all VisualSVN Server users update to the new builds.

You can get the latest version of VisualSVN Server on the official download page.

• Viewing Word, Photoshop and Illustrator files in the web interface.
• Blame/Annotate view in the web interface.
• New licensing model with Community, Essential and Enterprise licenses.
• A number of new and updated PowerShell cmdlets.

There are many other significant improvements related to various VisualSVN Server features, some of which are listed below. For the complete list of changes, see the VisualSVN Server 4.0.0 changelog.

Upgrade to VisualSVN Server 4.0 is recommended for all users. The upgrade is easy and straightforward, but it is highly recommended to read the KB149: Upgrading to VisualSVN Server 4.0 article beforehand (especially if you are upgrading from VisualSVN Server Standard Edition).

Download VisualSVN Server 4.0 from the main download page.

Viewing Word, Photoshop and Illustrator files in the web interface

VisualSVN Server 4.0 adds support for .docx, .psd and .ai files preview in the web interface. Viewing works entirely on the client-side (in the browser) and supports all standard kinds of the specified file formats. It dramatically improves the usability of VisualSVN Server and Subversion as a Document Management System (DMS).

Try the new feature by clicking one of the documents in the demo repository.

Blame/Annotate view in the web interface

VisualSVN Server 4.0 adds the Blame/Annotate view to the web interface. In the blame view, each line in the file gets annotated with the author, date and revision number of the most recent change. Blame view also features the Blame previous revision command that helps to efficiently examine blame results for earlier revisions.

Try the new feature in the demo repository.

New licensing model with Community, Essential and Enterprise licenses

The previous licensing model with a flat $950 price for Enterprise license was introduced back in 2010. A lot of things have changed since then, and that's why we have decided to make this change.

Starting from version 4.0, VisualSVN Server is available under three different licenses:

• Community license (free). This free and fully functional license enables core VisualSVN Server features such as the VisualSVN Server Manager MMC console, PowerShell Scripting and Automation, rich HTML5- powered web interface and support for secure HTTPS. The free Community license is available for commercial use and allows creating up to 15 Subversion user accounts.
• Essential license (paid). This license allows using all features of the Community license and adds additional features such as Scheduled Backup Jobs and Multisite Repository Replication (VDFS). The cost of the license depends on the maximum number of active users and the VDFS repositories allowed by the license.
• Enterprise license (paid). This license allows using all features of the Essential license and adds enterprise-grade features such as Windows authentication (including Active Directory Single Sign-On), Remote Server Administration, Access and Operational Logging and so on. The cost of the license depends on the maximum number of active users and VDFS repositories allowed by the license.

With the new licensing model, the minimal price for the paid Essential and Enterprise licenses is $55 and $350 respectively, and this makes paid features available to a wider range of users. At the same time, new licensing model provides a fundamental basis for further development of advanced enterprise features required by large customers. We are already actively working on exciting new features that will become available in the upcoming releases.

Consider the article KB146: VisualSVN Server 4.0 Licensing Overview for more information about the new licensing. You can see the current prices for the Essential and Enterprise licenses on the Licensing page.

What happens to existing Enterprise licenses?

To ensure a smooth transition for enterprise customers, all existing Enterprise licenses with an active maintenance are treated as valid licenses for VisualSVN Server 4.0 with an unlimited number of users and VDFS repositories. Thus, you can upgrade to VisualSVN Server 4.0 right now and without any unexpected expenses.

Moreover, all existing customers have an opportunity to renew their Enterprise licenses for the old $475 price (and for an unlimited number of users and VDFS repositories, too). This is a one-time opportunity available only for pre-4.0 licenses with an active maintenance subscription that were purchased before May 15, 2019. Further renewals will be processed using the new pricing model.

Are there any discounts for those who are upgrading from the Standard Edition?

We provide a 50% discount for all the existing customers who have more than 15 Subversion user accounts and are going to upgrade to the Essential license. Please use the RPCNTZ7TRL coupon code which is valid until September 1, 2019.

We also are going to provide a significant discount for all the existing customers who were using Windows Basic Authentication in Standard Edition and are going to upgrade to the Enterprise license. Please contact us at sales@visualsvn.com to get your individual coupon code. This opportunity is available until September 1, 2019 too.

A number of new and updated PowerShell cmdlets

VisualSVN Server 4.0 adds TLS/SSL server certificate management capabilities to the Get- and Set-SvnServerConfiguration PowerShell cmdlets and also introduces the following new cmdlets:

• New-SvnServerCertificateRequest: generates a Certificate Signing Request (CSR).
• Get-SvnServerLicense: returns details about the license installed on a VisualSVN Server instance.
• Set-SvnServerLicense: updates the license on a VisualSVN Server instance.
• Export-SvnRepository: exports one or multiple repositories.
• Invoke-SvnJob: runs a background job and waits until it completes.

For the complete list of available PowerShell cmdlets, see the KB88: VisualSVN Server PowerShell Cmdlet Reference.

Other VisualSVN Server 4.0 significant changes

VisualSVN Server 4.0 introduces a number of other significant improvements, such as the following:

• Updated look & feel of the web interface. The web interface received several look and feel tweaks and improvements including a new navbar and revamped Commit Details view.
• Downloading folders in the web interface. Any folder inside a repository may now be downloaded as a ZIP archive using the `Download` button.
• Linking to the specific line of code in the web interface. It is now possible to share links to specific lines of code at certain revision.
• Viewing password-protected PDF files in the web interface. It is now possible to view password-protected PDF files.
• New Export Repository wizard. The new wizard allows for exporting repositories in the form of hotcopy, dump or compressed dump.
• New option to Obtain certificate from Active Directory in the installer. There is a new option to generate the SSL/TLS certificate from your Active Directory Certificate Services when you install VisualSVN Server on a domain- joined computer.
• Self-service password changing for Subversion user accounts. VisualSVN Server 4.0 allows users to change their passwords via the web interface when your server is configured to use Subversion authentication.

Upgrade and compatibility concerns

Upgrade to VisualSVN Server 4.0 is recommended for all users. Read the KB149: Upgrading to VisualSVN Server 4.0 article before upgrading (especially when you upgrade from Standard Edition).

Starting from version 4.0, Standard and Enterprise Editions are replaced with new Community, Essential and Enterprise licenses. During the upgrade to version 4.0, your server will automatically switch to the new licensing model. If you are upgrading from Standard Edition, in most cases it will be automatically replaced by the free Community license. However, if you use Windows Authentication or if there are more than 15 Subversion user accounts, you will need to apply a sufficient Essential or Enterprise license key or start the 45 days evaluation period. For further details read the article KB147: How the licensing model changes in VisualSVN Server 4.0 for more information.

Starting from VisualSVN Server 4.0, the repository web interface no longer supports Internet Explorer 10. You need to upgrade to Internet Explorer 11 or use another supported browser with the repository web interface. Read the article KB151: Browsers supported by VisualSVN Server Web Interface for more information.

Word is either registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.

Illustrator and Photoshop are either registered trademarks or trademarks of Adobe in the United States and/or other countries.