I'd like it if the update (get latest version) window either stayed open after the update had completed, or there was an option to allow this. My reasoning is that information about what changes the update has performed are displayed in the window, along with the revision you are updating to, but since it closes as soon as it's finished you don't really get a chance to look at this information.

You should be able to add references , where the assembly is a local file in the solution directory, to Subversion more easily

Can ankh SVN be made to integrate with Microsoft Expression Blend Studio 3?

Two things from the top of my head around svn:externals that I think would be useful
1. Some GUI to easily add external folder (like project already being part of another solution in shared repository) to solution.
2. Some visual indication that project is an external reference.
3. Some indication that there exists newer version of the project being referenced in its original location. (i.e. when bugfixes have been introduced)

Applicable to unified diff command, show changes, annotate

If any violations are present then refuse commit.

It wuould be nice to prevent code that does not build to be committed. This would prevent broken code to go to the repository and no more broken build warnings from cruise control.

I have files in my project structure that are not part of the solution, nevertheless, i'd like to put them in svn.
The reason the files are not in the solution is that they are used to build the project, but are not part of the source distribution of the project. In this case i am talking about msbuild tasks files...

Multiple exclude lists to hide elements that should not (yet) committed, would be nice.

It would be very useful to be able to filter the history viewer for a particular user/developer. This has two benefits: 1) When performing code reviews it is helpful to see revisions pushed by a specific developer 2) Our CI system produces several checkins and having to wade through meaningless revisions (in the context of Visual Studio - the CI server checks in an obfuscator file which doesn't affect the solution).

This would allow using a subset of the AnkhSVN 2.X support from older Visual Studios and other applications that use the MSSCCI api.

Although TFS is generally used as a combined issue tracker and source repository, many of the projects at my company use SVN for source control due to legacy reasons and TFS for work item tracking.

I'd love to see the ability to link SVN changes to TFS Work Items using a built-in issue tracker extension.

we have a sln which contains about 30 projects. 2/3 of them in repository A,others in repository B. repository B contains all the helper projects like I/O read and write and so on.

when update reopsitory B, ankh update those porjects one by one, that's Low efficiency!!

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".

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.