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.
-
Better support of 'Web Site' projects
On Adding and Checkout AnkhSVN currently only handles projects in a single tree, just like all other Subversion clients.
The Visual Studio SCC api also allows SCC providers to support different layouts. E.g. a solution with libraries somewhere below 'D:\Projects' and a website on 'C:\inetpub\wwwroot\mysite' or a central server like '\\devserver\sites\my-site'
AnkhSVN should be extended to handle these layouts in both 'Add to Subversion' as Checkout scenarios. And via the scc-enlist support these paths should be per user definable to support different layouts on different systems. (On Checkout this could be a connect to an existing directory of a new… more
299 votes -
AnkhSVN should be localized to the same languages as Visual Studio
AnkhSVN should be better localized and language packs for all VS-Supported languages should eventually be available.
295 votesstarted ·
Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
I will start inviting translators around September 2011. (I hope to have a dummy translation ready by then) Please contact us via the mailinglist if you like to help.
[Updated to follow reality. Rescheduling now as Subversion 1.7 is on its way]
-
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.
239 votesunder review ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
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 that updates are logged to the Subversion page of the output window.
-
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)136 votes -
Expression Blend 3 Support
Can ankh SVN be made to integrate with Microsoft Expression Blend Studio 3?
130 votesunder review ·
Adminsrijken
(Admin, AnkhSVN & SharpSvn Projects)
responded
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 :-)
-
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
97 votesunder review ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
Looking at better options.
Current workaround is adding the files to a project or the solution.
-
Change the color of the color bar in Visual Studio
VS has the built-in behaviour of changing the colour bar (just to the left of the code) that tracks the change status of the code (yellow for unsaved code modification, green for code changed and saved this session).
VisualSVN makes a change to the colours of this colour bar, depending on the status of the file (unsaved or saved modification from working copy)?
Could AnkhSVN be modified to change the behaviour of this colour bar in a similar fashion (red for unsaved local modifications, yellow for saved modifications from the local copy) based on the SVN status of the line,… more
86 votes -
Add Option for Mandatory Comments on Commit
Add the Option for Mandatory Comments on Commit.
Forcing a comment to be made before commit is allowed.
Default setting for All New projects and Individual settings for existing projects.
85 votes -
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… more
80 votesunder review ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
Can you add an issue on our issuetracker to track this feature request?
-
Check StyleCop before commit
If any violations are present then refuse commit.
42 votesunder review ·Adminsrijken
(Admin, AnkhSVN & SharpSvn Projects)
responded
Quite a specific feature, maybe this should be implemented using client-side hooks that are described in another uservoice idea
-
allow comment templates
It would be nice if we could set up a template for commit comments so that we do not have to add a comment structure that we use to make comments look uniform
37 votesplanned ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
The right click —> Use template option will certainly work and fits nicely in the current workflow
-
Add option to ignore whitespace changes
Applicable to unified diff command, show changes, annotate
34 votesunder review ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
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.
-
33 votesstarted ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
Many commands are already available on the changed files list. We are working on the issues to also make them available on the top list (that doesn’t have a single file selection)
-
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 votesunder review ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
We currently recommend that we add files like this with operation ‘none’ to the project (or to a special project for these files: e.g. solution folder or C++ makefile project).
We are looking into extending this for future versions
-
Restore current commit message between visual studio sessions
I usually start to write a detailed commit message whitout commiting immediatly. The very annoying thing is that if I close visual studio (or if it crashes...) before commiting, my message is entirely lost. If you found a way to save this message this would be great !!
29 votesplanned ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
This is on our TODO list. It just needs a good design to work correctly (especially around VS crashes)
-
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.
29 votesunder review ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
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.
-
suggestions/autocomplete in commit message
It would be nice to have suggestions in commit message textbox, which would include file names, classes etc.
tortoisesvn has such feature
25 votesplanned ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
It’s on our todo list.
-
exclude lists
Multiple exclude lists to hide elements that should not (yet) committed, would be nice.
23 votes -
19 votes
-
Add the commit/update item in the editor context menu.
The commit/update item in the popup menu.Like VSS.
16 votesstarted ·Adminrhuijben
(Bert Huijben, AnkhSVN & SharpSvn Projects)
responded
Popup menu? You probably mean a context-menu somewhere, but on which control is the main question…
[Reporter answered: I mean when right-click on the Text Editor.]
Current status: This will be implemented with some extra UI updates to the commit dialog. (You will get into the commit editor of the project containing the file with the current file checked and other changes unchecked)
