AnkhSVN - General

Welcome to the AnkhSVN feedback forum. Do you have an idea? Do you recognize a good idea when you see one? We want to hear from you!

We track development issues in our issue tracker. Please add references to relevant issues.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Keep update window open after update complete

    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.

    272 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Flag idea as inappropriate…  ·  Admin →

    The update window is a modal dialog. If we were to keep this open, there’s no way to use Visual Studio without closing it.
    We will need to add another way to take a look at recent changed made by others by either caching the updated files list, or the before/after revision and showing the log messages between the two.

    Note:
    1) that update output is always logged to the Subversion page of the output window.

    2) All pending conflicts (even to files not referenced in the repository) are always shown in the pending changes window.

  2. Enable 'svn-add'ing references

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

    195 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Expression Blend 3 Support

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

    158 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    It’s not possible to use the current AnkhSVN inside Blend. Getting this done would mean implementing a new SCC provider for Blend (it has a very different interface), It does look like it’s a lot less work to do so. Keep the votes coming, and we might consider it :-)

  4. add better support for svn:externals

    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)

    139 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Auto check the server side for updates on opening projects

    It would be very useful to have some warning that the solution has been changed and the version on your machine is not the latest one - on opening the solution.

    Example:
    We have multiple developers working on the solutions in the repository.

    If you open a solution that has had changes made to it since the last time you opened it, you cannot tell that it has been changed until you do and update.

    If you forget to do this every time you could have a big problem when it comes back to committing it back to the SVN…

    89 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add option to ignore whitespace changes

    Applicable to unified diff command, show changes, annotate

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    We currently use the Menees tools for our internal diff viewer. This option will be enabled when we switch to the subversion diff library for creating the diff.

    This issue is fixed for the annotate viewer.

    Visual Studio 11 has a builtin diff viewer, which will automatically be used instead of the Menees tools. This diff viewer has many new options.

  7. Check StyleCop before commit

    If any violations are present then refuse commit.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. force a build before commit if build fails do not 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.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow to add files that are not part of the solution

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

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. exclude lists

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

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Working copy backup using diff/patch files.

    Add a "Backup working changes" button to the AnkhSVN toolbar. Configure the backup location in Tools > Options -> Source Control. Include tags in the path which can be replaced with the Solution name. This will allow developers to easily backup their current work without checking it into subversion. Having your working copy backed up to a network share, would be useful for day-to-day work that doesn't warrant its own feature branch.

    An option to automatically backup at regular intervals would minimize lost work in the event of a machine failure.

    This could possibly be scripted using the command line,…

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Currently a patch file can’t express all information in a working copy. A new feature partly available in subversions trunk should make it possible to fully capture all changes (including copying and renaming files) in the new svnpatch format.

    A full implementation of this feature will probably require Subversion api changes that are scheduled for 1.7 or 1.8.

  13. Add Username Filter to History Viewer

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

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add mini-AnkhSVN plugin implementing the old MSSCCI api

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

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add TFS issue tracker integration

    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.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support multi repository more efficiency?

    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!!

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Fix 'Failed to save open documents before committing' error

    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.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow reverting of delete file commits

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

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Ability to set svn properties on multiple files at once and on entire folder recursively

    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.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. browse for repository

    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.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    We recommend not to use file:/// based repositories as those don’t allow the full power of subversion (and it breaks the failsafe atomic commit support if you use network paths).

    That said, we use the .Net Uri class to parse the uris and those automatically convert paths like ‘C:\repository’ to ‘file:///C:/repository’; for you. (so while it is not a documented feature it is pretty easy to paste local paths)

← Previous 1
  • Don't see your idea?

AnkhSVN - General

Feedback and Knowledge Base