It is not necessary to show an unmodified icon if a file isn't modified. The solution explorer will look cleaner with less noise. Please add at least an optional setting for this.3 votes
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
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
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
I can see a new issue in 2.3 (SVN 1.7) - when I update from the Pending changes, some files are for a brief moment shown as red (changed, added, or deleted). This happens only for a short while and disappears once the update is completed.1 vote
Known issue. While updating we sometimes receive external file changed events, but in these cases Subversion doesn’t allow checking the status. This causes them to show up as new file.
It would be nice if we can suppress these unneeded events.
"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.6 votes
You should be able to add references , where the assembly is a local file in the solution directory, to Subversion more easily195 votes
Looking at better options.
Current workaround is adding the files to a project or the solution.
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.275 votes
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.
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.
when I commit in Visual studio, this screen appears:
"You are trying to commit files from several subversion working copies. Which working copies would you like to commit with the current log message?"
After this there is a list of paths. My question is: is there a way to remove all these paths. I only need one of them and now I always need to check/uncheck the right one out of this list.
This tracker is for ideas, not for bug reports and questions. (Use email@example.com for that).
Your fix would be to not select files from multiple working copies or if the multiple working copies are from a single repository: to wait for Subversion1.7 / AnkhSVN 2.3, which will allow committing from multiple repositories at once.
Moving a target to the ignore-on-commit list will make sure it isn’t checked by default.
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
Great product. I want to pay2 votes
As some of you might (or might not) know my work on AnkhSVN, SharpSvn and Subversion is paid by CollabNet.
So the development is partially funded by companies that subscribe to CollabNet support packages (which btw. include AnkhSVN support).
We are currently not looking at opening other ways of funding, but casting a lot of votes on this request might make us change our mind.
The context menu for modified files in the Pending Changes tool window is lacking an "Open With..." item.
"Open With" is useful when reviewing changes that open up a full designer - for example, complex XAML Workflows can take a very long time to open and occasionally it makes more sense to open them with the XML Editor.
This is true for just about all files with designers.1 vote
Can ankh SVN be made to integrate with Microsoft Expression Blend Studio 3?158 votes
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 :-)
Multiple exclude lists to hide elements that should not (yet) committed, would be nice.24 votes
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
If any violations are present then refuse commit.45 votes
Quite a specific feature, maybe this should be implemented using client-side hooks that are described in another uservoice idea
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
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
This looks like a great suggestion for an AnkhSVN-Addin.
This feature wouldn’t be generally usable as Subversions mixed revision working copies make it impossible to guarantee that a local successful build is succesfull on a different pc.
Currently the Repository Explorer shows the current state of the repository. It would be nice to be able to see an older state (ie. older revision).
For example, if a file or directory is deleted, currently the only way to find it is to browse through the History Viewer, trying to find it there.1 vote
This is a valid use case, but I would prefer a separate window for browsing through the repository as it was some time ago
- Don't see your idea?