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.Fadi Abou Dib commented
I appreciate having the dialog close automatically at times to speed things up. However, at other times, this can really bother me. I believe it depends on the project, and on who you're talking to (developer, project manager...). How about adding a global setting in the form of a checkbox through which you can opt-in to keep the dialog open when updating is done. If this can be done on a project basis, I believe it would be much better, however, I doubt that can be achieved.Fadi Abou Dib supported this idea ·