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.
Thanks to Bert Huijben for pointing out why NuGet packages folder should be excluded from the repo. How about another approach: i.e. that AnkhSVN automatically triggers a "nuget install packages.config" when this file is updated via SVN update?3 votes
I think this should be implemented in NuGet on a file change/reload event from Scc providers. This would also allow the same update from TFS, VSS, etc.
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 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
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.
I want do something such as(run a exe\bat) after (or before) Do commit.3 votes
This request should be handled with our TortoiseSVN client hook compatibility which is currently being tested.
(Can be enabled via the registry in the daily builds of AnkhSVN 2.3)
This feature will be enabled by default in a future release.
Make issue tracker "YouTrack" available for VS2010 integration.56 votes
Monitor for changes to files in your project and in the .svn folders and automatically refresh the SVN change status. This will make using third-party tools easier, like Expression Blend.29 votes
When a file is locked, but no other changes have been made to the file, "Commit changes" becomes active in the interface, but selecting it does not unlock the file (and therefore commit changes remains active). This behaviour also exists in Tortoise, but is equally annoying there.9 votes
I agree, performing the unlock operation (by pressing Commit) would be a nice thing to do.
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.
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
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.
I cannot see the Issue tracker setup in my solution explorer
My Issue tracker is JIRA4 votes
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.4 votes
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.8 votes
Currently if a message is added to the pending changes tab, it will be discarded upon closing visual studio. It'd be nice if these could be kept between sessions, to help remember any changes since the last commit...19 votes
It’s on the TODO list and should be available in the near future.
- Don't see your idea?