Very good extension for subversion support from within Visual Studio. Well done.
One thing I noticed is that in Visual Studio 2012 the checkbox to check or uncheck all pending changes at once is missing. In VS 2010 it's there. I don't know why this is the case but is it possible to fix this? Because this functionality is used very often. It is currently quite annoying to uncheck every changed file manually.
[Update]: I just realized, that the check box on top is only missing when I use the 'Dark' theme. When switching to the 'Light' theme, it is there. Switching back removes it...
i have two projects include within the same solution. One is a resusable componet that will be compiled seperately and then later included just as a dll. For now, when i have both projects open in the same solution and i perform an update, it only updates the code under the one of the repositores and excludes any updates from the other. When i do a commit it is able to tell that their are multiple differrent SVN repositories and it asks me chich ones i would like to commit against. It would be great if the update would update all resources under the main solution
AnkhSVN - Subversion Support for Visual Studio 2.5.12266.473
* Ankh.Package 2.5.12266.473
* Subversion 1.8.4 via SharpSvn 1.8004.2605.15365
SharpSvn is linked to: Apr 1.4.8, Apr-util 1.5.2, Cyrus Sasl 2.1.23, OpenSSL 1.0.1e 11 Feb 2013, serf 1.3.2, SQLite 3.7.17, Subversion 1.8.4-SharpSvn-1.8.4, ZLib 1.2.8
SharpSvn is optionally linked to: Berkeley DB 4.4.20, SharpPlink 1.8004.2605.15365
Hi guys, running vs2013 on a SSDT project but with all the Productivity Power Tools extensions enabled (I think except Structure Visualizer) and running ankhsvn, if I rename a file (that is already committed to the repo) I get a COM error E_FAIL.
If I disable all the individual productivity modules in options I can rename the file. I have successfully used Color Printing, Fix Mixed Tabs, Middle-click scrolling, Solution Error Visualizer, Structure Visualizer, Syntactic Line Compression.
Sorry I ran out of time for experiments. It may be an issue with Productivity Power Tools (and have raised to them also) but thought I'd see if you know of the issue
running AnhSVN v2.5.12471.17
Productivity Power Tools v12.0.30519.1
I have 2.4.12012.1 connected to a 1.7 server.
If i use the current update to 2.5.12040 the complete project is shown that it would need an update, and therefore is not available for source control.
I uninstalled 2.5.12040, installed 2.4.12012.1 and everythign is fine.
Now I get an pending update for Ankh which I do not want to install for obvious reasons.
How can I get rid of the update message, so that the VS tray notifier only shows other updates, if new ones are available?
Or do i need to uninstall ankh completly and go for another SCC?
We can't reproduce this issue without more information, nor did we hear about this on our user support list over the last few months.
Make sure you report crashes Visual Studio crashes to Microsoft as they actively look at it and contact addin vendors if they determine a root cause of common problems.
When i opened source from subversion, visual studio 2010 pro encountered a problem and stating that either need to restart studio or close it.
VS 2010 Pro is working fine when i work offline.
Anyone face the same issue, need help...
Downloaded 2.5.12116.397 and installed to VS2013. Similar problem to the other poster:
SharpSvn.SvnSystemException: Commit failed (details follow): ---> SharpSvn.SvnSystemException: Unable to connect to a repository at URL 'http://svn.internal.server/svn/repository/Source/App/Presentation.Web' ---> SharpSvn.SvnSystemException: Error running context: No connection could be made because the target machine actively refused it.
The SVN machine is remote. I also have to do all my commits via TortoiseSVN from Windows Explorer.
Is this a similar problem? Just have to wait until the next release?
i update my tortoise svn to 1.8 and download least version 2.5 ankh
but now i can not update or commit my project within visual studio 2012
SharpSvn.SvnSystemException: Commit failed (details follow): ---> SharpSvn.SvnSystemException: Unable to connect to a repository at URL 'http://localhost:8080/site/sampleweb' ---> SharpSvn.SvnSystemException: Error running context: No connection could be made because the target machine actively refused it.
--- End of inner exception stack trace ---
i always commit using tortoise svn
The 'serf' HTTP library that is used by the Subversion libraries prefers ipv6 over ipv4 and assumes that if a host resolves to both addresses the ipv6 address works. localhost resolves to ipv6 and ipv4.
The recent daily builds contains a serf patch that reintroduces the old neon behavior of trying multiple addresses if connecting to the first address fails. A new full release with this support enabled should be out soon.
Installed latest ankhsvn 2.5.12116.397 after installing VS2012 alongside my current VS2010sp1 install.
Wehn opening VS 2010 solution in VS2010 I now get the dreaded:
"Subverison detecetd a working copy that needs an explicit upgrade in ..."
It seems to be complaining aabout a particular project in the solution, which is actually an svn:external to a branch of another solution.
this has never caused any issues before.
After reeading posts on here and stackoverlfow I upgraded my tortoiseSVN to latest 64bit release. This taken from my tortoise About dialog:
TortoiseSVN 1.8.2, Build 24708 - 64 Bit , 2013/08/27 19:20:39
Subversion 1.8.3, -release
Can someone help - this is driving me insane!
Every working copy (including every directory external, which is a working copy) must be in the right working copy format for it to be used by the Subversion libraries.
The specific working copy noted in the dialog is not yet upgraded, and needs an explicit upgrade via either AnkhSVN, TortoiseSVN (or any other Subversion 1.8) based subversion client. In AnkhSVN this is usually as easy as right clicking some file/directory in the working copy and selecting 'Upgrade Working Copy'.
Before Subversion 1.7 the Subversion project automatically upgraded working copies, so you wouldn't see such errors. But if you accidentally upgraded a working copy there was no easy way back.