I would have submitted this to the issue tracker or mailing list, but both were so user-unfriendly that I thought I'd do it here.

The issue (present in 2.1.10129.17) seems to be that, when no documents are open in VS, committing changes results in an error dialog saying "Failed to save open documents before committing." I finally figured out a workaround - open a document before trying to commit.

Once a file deletion has been committed, it is extremely difficult to undo this. The only way I managed to do it was to find the revision where it occurred in the History Viewer, choose "Revert changes from this revision" (thereby reverting all the changes done there) and then again reverting the other changes.

Much simpler if I could select the "delete file" action in the History Viewer's changed paths and choose "Revert".

AnkhSVN with VS2017:

Project member files fail to appear in the Pending Changes window. Some part of the VS2017 / AnkhSVN combo misplaces the fact that the file is part of the project, per the Source Control Info panel. Loading the solution afresh works around the problem, but is not acceptable.

See this thread for more detail:

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

I want to be able to push out the change log for my class libraries as text or rtf with my dll. For solutions I could see ways to auto generate change logs accessible from inside a program. A command line option would be nice for pre-build scripts, but a gui option would suffice.

I have no idea if this is even possible, but it would be very cool if the icon displaying the status of a file (new, added, modified, etc.) could also be shown in the tab of the documents.

I tried to fake an image to explain what I mean:

http://img265.imageshack.us/img265/522/ankhsvnstatusintabs.gif

Although this may be possible using a pre-build script/macro, it would be great to have the ability to automatically update the revision part of the AssemblyFileVersion attribute each time the solution is built.

Currently svn properties can be set only for a single file at once, for example, the 'svn:needs-lock' property.

It would be great if this could be done for multiple files at once or an entire folder recursively.

I use the file system based repositories primarily and having to go into explorer, get the path, feed it through a text transformer to change the \ to /, then add in the file:/// in a text box that isn't big enough seems like way more steps than necessary.

"Needs-lock" files must be locked before editing. When Server is not available, ReadOnly attribute (R) must be deleted with File-Explorer, should be possible within Viaual Studio.

AnkhSvn annotate shoudl offer a option like TortoiseSVN blame to include the merge information.

It would be great if a simple spell/grammar check was added to AnkhSVN, I often find myself double checking my grammar using word or at times even gmail. A spell checker is so common nowadays that I was quite surprised it is not yet on the roadmap. It reduces the amount of (unintended) typos ending up in the repository history, a must have for enterprise grade tooling.

I was not able to find anything in Ankh ( Visual Studio) which lets me browse conflicted files.

Note that some of the resolve options (e.g. Edit Conflicts) require a merge tool to be setup in Tools -> Options -> Source Control -> Subversion user tools

Would like to view and edit the conflicts in Ankh itself.

Currently the only thing I resort to tortioseSVN for is gui based repository creation. Then I have to feed the explorer path through a text transformation to fix the \ to / then append a file:/// in a textbox that by default doesn't accomdate the extremely long paths I have here at work.

I'm using the dark theme in VS2013 and I can barely see the changeset title headers in the pending changes window.

They are set to a dark blue with a dark background. While the dark blue is a nice fit for the default theme it is not for the dark theme.

Please add a section in Font & Colors settings of VS.

I really only care about the filename and maybe the parent folder of what ever file is being effected. Currently right now you see the whole path meaning every time I commit I have to make the columns bigger to see what I am commit and I have to resize it every time.