AnkhSVN & SharpSvn Projects on UserVoice

Expression Blend 3 Support [updated]

2012-05-15T02:21:33-07:00

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

harris said:

Really need this :(

the min log size?

2012-05-03T20:03:48-07:00

zhangxh suggested:
does AnkhSVN can set the min log size as TortoiseSVN use tsvn:logminsize property?

Fix font size on website

2012-05-02T02:40:04-07:00

an anonymous user suggested:
The font size is too large and overflows the boxes.

Fix 'Failed to save open documents before committing' error [updated]

2012-04-26T13:02:29-07:00

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.

rhuijben said:

Any idea which kind of documents were open within reach of the commit?

We just ask Visual Studio to perform a Save operation on the documents that are open within the commit. This message is the result of a document that says it can't be saved.

So whatever we would commit here might not be what you expect, as the document reports that it has in-memory changes that can't be saved.

Fix 'Failed to save open documents before committing' error [updated]

2012-04-26T12:02:10-07:00

Preston McCormick said:

I have been getting the same error lately. In my case the work-around was ineffective.

Add client side hooks, like those in TortoiseSVN [updated]

2012-04-12T18:41:46-07:00

Mark Walker said:

Awesome, thanks :)

default from/to comparison [is now planned]

2012-04-12T15:51:13-07:00

When diffing a file, I'd like to be able to set the default from type and to type that are specified so that the shift key bypass is more useful to me. The defaults of Base and Working are useless to me as that shows what I've done locally - which, if I'm committing as often as I should, I know what I've done. Being able to default to Latest Version instead of Base would save me lots of clicks.

history window: View file [is now planned]

2012-04-12T15:49:33-07:00

I'm missing a simple feature; viewing a file from the history window (no diff) and if possible from an external editor.

Add FogBugzID box to Interface. [is now completed]

2012-04-12T15:47:14-07:00

Add FogBugzID or whatever, to the AnkhSVN interface if the properties exist in the Subversion Repository.

Add FogBugzID box to Interface. [updated]

2012-04-12T15:47:13-07:00

Add FogBugzID or whatever, to the AnkhSVN interface if the properties exist in the Subversion Repository.

rhuijben (admin) responded:

This feature is already available in all recent AnkhSVN versions. Just make sure the properties are stored on either the project root (=working copy root, unless otherwise specified in File->Subversion->Change Source Control) or the solution file. AnkhSVN doesn't check other locations for performance reasons

Add Username Filter to History Viewer [is now under review]

2012-04-12T15:44:48-07:00

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

Deliver Ankhsvn as VSIX! [is now declined]

2012-04-12T15:44:08-07:00

For VS2010, it would be great to have Ankhsvn delivered as a VSIX package.

Deliver Ankhsvn as VSIX! [updated]

2012-04-12T15:44:08-07:00

For VS2010, it would be great to have Ankhsvn delivered as a VSIX package.

rhuijben (admin) responded:

For VS2010 this is not possible, because that would break our issuetracker integration (which requires a version rebinding manifest)

Add client side hooks, like those in TortoiseSVN [is now completed]

2012-04-12T15:40:50-07:00

Add client side hooks, like those in TortoiseSVN [updated]

2012-04-12T15:40:50-07:00

rhuijben (admin) responded:

Support for automatically running TortoiseSVN pre-commit and post-commit hooks is available in te daily builds and will be available in the next release

support for fog bugs bugzid propset [is now completed]

2012-04-12T15:35:14-07:00

did the following http://www.fogcreek.com/fogbugz/docs/70/topics/sourcecontrol/setup/TortoiseSVN.html TortoiseSVN is now showing an extra text box for the entry of the bug id this had no impact on the commit window with Ankh, would be VERY helpful.

support for fog bugs bugzid propset [updated]

2012-04-12T15:35:14-07:00

rhuijben (admin) responded:

This issue has been implemented in AnkhSVN for quite some time. Make sure you have the properties on the directory that AnkhSVN notes as the project root in File->Subversion->Change Source Control (usually the working copy root) *or* on the solution file.
(This last option is to allow different settings for AnkhSVN and other tools).

Note that the edit box is automatically hidden if the issue regex feature is used.

Add Username Filter to History Viewer

2012-04-04T07:24:05-07:00

Kevin McCormick suggested:
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).

not working in vs 2010 [is now declined]

2012-03-21T03:37:11-07:00

not working in my visual studio the addin installer install sucessfully but unable to register with my visual studio

not working in vs 2010 [updated]

2012-03-21T03:37:11-07:00

not working in my visual studio the addin installer install sucessfully but unable to register with my visual studio

srijken (admin) responded:

Not a new "idea" or feature, this should work. Please contact the mailinglist/forum: http://ankhsvn.open.collab.net/ds/viewForumSummary.do?dsForumId=582

Keep update window open after update complete [updated]

2012-03-20T16:20:17-07:00

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.

rhuijben (admin) 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.

Keep update window open after update complete [updated]

2012-03-20T13:56:45-07:00

Samuel Tremblay said:

Is there any workaround to show a history of changes now?

With the new version the "Update" is not mandatory before committing [is now declined]

2012-03-12T05:58:31-07:00

In previous versions, when I commited the changes and the server code had chaged, the plugIn forced me to Update to the last version. I consider this an important feature because I can prevent the conflicts before commiting. Is this a lost feature or do I have to configure it ? Thanks for your your.

With the new version the "Update" is not mandatory before committing [updated]

2012-03-12T05:58:31-07:00

rhuijben (admin) responded:

Nothing changed. When you commit the server determines if updating is necessary and in that case AnkhSVN will report you that it is necessary before the commit.

If it isn't necessary you aren't warned... It's very easy ;-)

support for fog bugs bugzid propset [updated]

2012-03-07T08:10:22-08:00

Greg said:

According to the comment by "nickyt" on this page, support was added back in 2010:
http://www.techques.com/question/1-1561103/Checking-in-Files-via-AnkhSVN-not-prompting-to-enter-FogBugz-Case-Number

I'm guessing nickyt was referring to the fact that if you manually type in "BugzID: #" as the first part of your commit comment, it'll work. But that has nothing to do with AnkhSVN, that is handled by the post-commit hooks on the SVN server.

I'm experiencing the same thing chris is, AnkhSVN is not prompting for the BugzID when committing changes. This would be VERY helpful in having developers specify the BugzID more often than not.
The fact that it's not prompting for it is almost a deal breaker. Really.

Fix 'Failed to save open documents before committing' error [updated]

2012-03-04T05:45:46-08:00

Anonymous said:

Restarting Visual Studio fixed it for me

NuGet refresh on SVN update of project packages.config [updated]

2012-02-27T15:51:16-08:00

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?

rhuijben (admin) responded:

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.

Better support for Reporting Services projects in VS 2005 [is now completed]

2012-02-27T15:49:38-08:00

Currently there are no icons displayed in VS 2005 for RDL files or other files (PNG, BMP, etc.) in report projects. While they are managed alright, it is a bit confusing not to get any visual feedback for those files.

Better support for Reporting Services projects in VS 2005 [updated]

2012-02-27T15:49:38-08:00

rhuijben (admin) responded:

This project type requires to be connected to source control. Click Add to Subversion on the project node in the solution explorer and everything will work.

(See also our frequently asked page:
http://ankhsvn.open.collab.net/wiki/Faq )

SVN 1.7.1 [is now none]

2012-02-27T15:48:22-08:00

Will you have another release to support 1.7.1 or can the current version support that?

SAck [is now none]

2012-02-27T15:48:15-08:00

Cannot download from http://ankhsvn.net/downloads/2.3/ Page will not load

Bug - VS2010 Class View is very slow [is now under review]

2012-02-27T15:47:57-08:00

Upgraded from 1.6 to latest 1.7 download. also tried daily update 2.3.10697.1155 and saw the same issue. CPU hits 100% (single CPU of 8) and class view updates very slowly. Also mouse over class view window produces the same issue. Using latest VisualSVN server and updated working copy to current svn format.

question: [updated]

2012-02-27T06:19:29-08:00

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

rhuijben (admin) responded:

This tracker is for ideas, not for bug reports and questions. (Use users@ankhsvn.open.collab.net 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.

Show the "Subversion" context menu entry for ASPX/ASCX files [is now completed]

2012-02-27T06:07:32-08:00

When inside a ASPX/ASCX file (in Source-View), the context menu does not contain the "Subversion" entry (e.g. to show the file's history or changes).

Show the "Subversion" context menu entry for ASPX/ASCX files [updated]

2012-02-27T06:07:32-08:00

When inside a ASPX/ASCX file (in Source-View), the context menu does not contain the "Subversion" entry (e.g. to show the file's history or changes).

rhuijben (admin) responded:

This feature is available since the last release and further extended to a few more editor types in the next release.
Note that the subversion dialog is always available on the tab in the document-well (the bar with the document titles), even for the most customized editors.

The commit dialog should have default focus on the message textbox to allow immediate typing [is now completed]

2012-02-27T06:04:27-08:00

The commit dialog default the focus on the message textbox to allow immediate typing.

The commit dialog should have default focus on the message textbox to allow immediate typing [updated]

2012-02-27T06:04:27-08:00

The commit dialog default the focus on the message textbox to allow immediate typing.

rhuijben (admin) responded:

This appears to be a regression. Fixed in last release.

Add option to ignore whitespace changes [updated]

2012-02-27T06:03:09-08:00

Applicable to unified diff command, show changes, annotate

rhuijben (admin) 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.

Bug - Freeze [updated]

2012-02-27T03:14:57-08:00

After a few changes in my windows form (c#) solution i can´t commit. I think it opens a new window after the click on commit, because visual studio 2010 lost the focus. But i ca´n´t see anything and so Visual Studio 2010 is freezed.

Anonymous said:

Yes, Tortoise was also installed on my system. I deinstalled Tortoise and reinstalled AnkhSVN, but same problem.

Newest Version of AnkhSVN, Windows 7 and VS 2010 with all updates

Bug - Freeze [updated]

2012-02-27T02:11:42-08:00

Anonymous said:

I Have exactly the same problem. I think problem started when i installed new version of Tortoise. I'm trying to commit by svn+ssh connection. It happens only when i'm using context menu commit.
Windows 7, vs 2010.

bug report? D/L link is broken...

2012-02-13T22:36:39-08:00

Faizan Kazi suggested:
Your download link seems to be broken: http://www.open.collab.net/downloads/subversion/thankyou_ankh.html?_=d

Monitor for file changes and auto refresh status [updated]

2012-02-11T08:32:53-08:00

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.

Paul Turner said:

Most of my team prefers to use TortoiseSVN for commits and updates, but use AnkhSVN for at-a-glance change visibility and SVN-Delete and SVN-Move integration into the IDE.

This feature will make it much easier to use AnkhSVN with other SVN-based tools like Tortoise. The code to perform a "refresh" already exists, so this might not even require a large effort.

Display status of a file in the document tab [updated]

2012-01-31T02:32:49-08:00

I have no idea if this is even possible, but it would be very cool if the icon displaying the status of a file (new, added, modified, etc.) could also be shown in the tab of the documents. I tried to fake an image to explain what I mean: http://img265.imageshack.us/img265/522/ankhsvnstatusintabs.gif

Martin said:

Maybe with VS 2012 ?

deliver the application to my home [is now declined]

2012-01-27T15:08:24-08:00

deliver the application to my home

deliver the application to my home [updated]

2012-01-27T15:08:24-08:00

deliver the application to my home

srijken (admin) responded:

I don't see a way to do this

Show the "Subversion" context menu entry for ASPX/ASCX files [updated]

2012-01-26T06:18:56-08:00

When inside a ASPX/ASCX file (in Source-View), the context menu does not contain the "Subversion" entry (e.g. to show the file's history or changes).

Martin said:

Thanks for the hint about the document tab!
This already makes it so much easier since it's no longer required to go the the solution explorer for the subversion commands.

Show the "Subversion" context menu entry for ASPX/ASCX files [is now under review]

2012-01-26T05:28:33-08:00

When inside a ASPX/ASCX file (in Source-View), the context menu does not contain the "Subversion" entry (e.g. to show the file's history or changes).

Show the "Subversion" context menu entry for ASPX/ASCX files [updated]

2012-01-26T05:28:33-08:00

When inside a ASPX/ASCX file (in Source-View), the context menu does not contain the "Subversion" entry (e.g. to show the file's history or changes).

rhuijben (admin) responded:

Technically this is probably an issue in the editor as it should re-use the standard menu, but I'll check what I can do.

Good suggestion.

For the most important commands you can work around this problem by right clicking on the document tab. That should work for all editors, including designers.

Different Builds [updated]

2012-01-20T03:52:34-08:00

Different builds for inexperienced Programmers would be nice. (For example some basic Builds with only basic functions like update checkout...)

Wolfgang said:

What is about this?

Bug - Freeze [updated]

2012-01-17T09:01:10-08:00

Anonymous said:

At "Pending Chanes" there is also a button "Commit". When i use this button and not the context menu in the project view it works perfect.

PS: At the main page at http://feedback.ankhsvn.net is a textfield with the text "- enter your idea (new feature, fix bug, etc) -"