List Pending Changes Browser
for Microsoft® Visual Studio® 2005 Team Edition for Software Developers
List Pending Changes Browser is a free software.
If you have ever needed to find out who has checked out files from your project on the Visual Studio Team System source control then the only solution was to browse through all the folders of your project in the Visual Studio Source Control window. Because this is such a common issue, Ekobit has developed a small Add-In for Visual Studio 2005 which can help you solve this problem.
List pending changes browser is a small Add-In (technically it is a VSIP package) for the Visual Studio 2005 Team Edition for Software Developers which enables you to view who has checked out what in your project. It adds a new tool window (List Pending Changes) to the Visual Studio 2005 collection of tool windows.
Using the List Pending Changes browser is relatively simple. You can access the browser from the View menu -> Other Windows -> List Pending Changes menu item. In order to list checked out files you must fill out the Path input field. Path input field represents the root of your search and it must be in Visual Studio Team System source control path format (example: $/MyProject). Beside entering the path manually you may use the Path field as a combo box and select the path from the given list of paths. Details...
|
The list of paths that will be displayed in the Path combo box drop-down depends on the Filter input field. If the filter input field is empty then you will see all the possible paths starting from the source control root. If the filter input field is not empty then you will see all paths where the filter matches the path. Wildcards (*) are also permitted and by using them you can filter by parts of the path.
Filter examples:
| Filter |
Meaning |
| (empty string) |
If you have not set anything for the filter then all possible paths will be shown (the entire hierarchy of the source control, starting from the source control root will be displayed) |
| TestManager |
All source control paths which have "TestManager" as a part of their paths. The following paths would be matched and displayed in the Filter dropdown:
- $/Ekobit/VSTS/TestManager - $/Ekobit/VSTS/TestManager/GUI - $/Ekobit/VSTS/TestManager/Resources - $/Ekobit/Licenses/TestManager
The following paths would NOT be matched:
- $/Ekobit/TestManagerLicense - $/Ekobit/InstallerTestManager |
|
*TestManager |
All source control paths which have "TestManager" with any prefix as a part of their paths. The following paths would be matched and displayed in the Filter dropdown:
- $/Ekobit/VSTS/TestManager - $/Ekobit/VSTS/TestManager/GUI - $/Ekobit/VSTS/TestManager/Resources - $/Ekobit/Licences/TestManager - $/Ekobit/InstallerTestManager
The following paths would NOT be matched:
- $/Ekobit/TestManagerLicense |
|
*TestManager* |
All source control paths which have "TestManager" with any prefix or suffix as a part of their paths. The following paths would be matched and displayed in the Filter dropdown:
- $/Ekobit/VSTS/TestManager - $/Ekobit/VSTS/TestManager/GUI - $/Ekobit/VSTS/TestManager/Resources - $/Ekobit/Licences/TestManager - $/Ekobit/InstallerTestManager - $/Ekobit/TestManagerLicense | |
Copyright notice: Microsoft, Visual Studio 2005 and the Visual Studio 2005 Team System logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.