Installation of AnkhSVN Visual Studio 2019

Question

I can not Install AnkhSVN -Subversion Support for Visual Studio 2019,

I have tried to Install It, It says Version is Invalid for VS2019

I use VS2019 Professional

Answer 1

I have made a fork of the AnkhSVN project and published a version on Visual Studio Marketplace as AnkhSVN2019.

This version targets only Visual Studio 2019.

The page on the Visual Studio Marketplace is here:
https://marketplace.visualstudio.com/items?itemName=PhilJollans.AnkhSVN2019

You can also find it by searching the Visual Studio Marketplace in Visual Studio.

The project is on GitHub here:
https://github.com/PhilJollans/AnkhSVN2019

As far as I can tell it is working correctly, but that is based on a small number of systems, and I only use a subset of the features.

Answer 2

Looks like it doesn't support VS2019 by default. https://ankhsvn.open.collab.net/ But you can try to update extension for VS2019.

1. Rename vsix to zip
2. Unzip
3. Open extension.vsixmanifest, manifest.json and catalog.json and for Microsoft.VisualStudio.Component.CoreEditor change version to [15.0,)
4. Open extension.vsixmanifest and also replace all [15.0,16.0) by [15.0,17.0)
5. Zip all files
6. Rename to vsix

Answer 3

I've just installed AnkhSVN 2.8.12824 via "Manage Extensions". It seems to work, though Visual Studio 2019 complains that it might not be compatible with a future Visual Studio update (Deprecated APIs).

See also https://ankhsvn.open.collab.net/ds/viewMessage.do?dsForumId=582&dsMessageId=647485

Possibly also https://docs.microsoft.com/en-us/visualstudio/extensibility/synchronously-autoloaded-extensions?view=vs-2019

Answer 4

The latest AnkhSVN version is not compatible with Visual Studio 2019 (and the project, unfortunately, seems dead).

A possible solution is to edit manually the files stored in the vsix file (it's a zip file with a different extension).

The file to edit are:

• extension.vsixmanifest
  Change the occurance of [15.0,16.0) to [15.0,17.0)
  Change the prerequisite in this way:
  <Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0,)" DisplayName="Visual Studio core editor" />

• catalog.json
  search Microsoft.VisualStudio.Component.CoreEditor and change the version to "[15.0,)"

• manifest.json
  search Microsoft.VisualStudio.Component.CoreEditor and change the version to "[15.0,)" as the catalog.json

After these changes it's possible to install the extension in VS2019 but still open a warning shown by VS related an incompatibility of the load process (AnkhSVN use a synchronous load, VS2019 want an async load).

Answer 5

AnkhSVN supports Visual Studio 2019 now. Download here https://marketplace.visualstudio.com/items?itemName=simonp.AnkhSVN-SupportVS2019 [broken link]

Seems to still be active on GitHub: github.com/simonp22/AnkhSVN

The owner removed the program from the marketplace until he works out the async loading in the code, according to a comment from him in the github project https://github.com/simonp22/AnkhSVN

Answer 6

The original AnkhSVN project developed by CollabNet is now abandoned and does not support Visual Studio 2019 now (the project is inactive for more than 17 months). As an alternative, consider migrating to VisualSVN that is now completely free for use on non-domain computers (no registration required) and provides about the same functionality compared with AnkhSVN (some users consider VisualSVN to be better for their use cases).

Migrating from AnkhSVN to VisualSVN is a straightforward process. The most recent VisualSVN 7.1 and VisualSVN 6.5 releases add support for multiple working copies within a single solution, and this makes the migration practically instant and painless for almost all users. See the article KB58: Migrating from AnkhSVN to VisualSVN for instructions and the article KB7: Using Multiple Working Copies in VisualSVN if your solution projects span across multiple working copies.

Note that the workarounds suggested in the accepted answer may cause overall Visual Studio destabilization and do not make AnkhSVN compatible with Visual Studio 2019. See the comments under these answers:

• https://stackoverflow.com/a/55533335/761095
• https://stackoverflow.com/a/55533472/761095

BTW, according to this post, those hacky workarounds do not work anymore.

DISCLAIMER: I am a support engineer with VisualSVN Team.