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.Suma shared this idea ·
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.Suma commented
This is on our TODO list. It just needs a good design to work correctly (especially around VS crashes)
It’s on the TODO list and should be available in the near future.
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.Suma commented
Maybe someone is not aware the is a workaround for this: list of updated files can be found in the Output window, in the "section" called Anhk - Subversion.