After installing this extension some of the icons of my Team Explorer became very weird. Some folders got the icon of a branch(yellow colored icon). The same for some of the xml files, sln files,... After disabling the extension, the icons turned back to normal.
How can I get your email address to send you some screenshots?
Hi, this worked great for a while and then, without any obvious reason, it started throwing an "TF10125: the path '$' must start with $/" error dialog. I uninstalled the TFS power tools to see if the error would be thrown with the power tools uninstalled and it was. I then uninstalled the extension and am no longer using it. I hope this bug is reproducible and can be fixed. The extension was great while it worked.
Yes Filter Folders by folder mapping feature works in VS2012 too.
Feature enable filtering of folders in Source Control Explorer treeview to only mapped folders in the currently selected workspace. So to use it, you must have root folder not mapped and use mapping only on some subfolders.
Sorry I didn't see your question as I would have voted "Yes". It's easier to tell fellow developers to cloak folders they don't want to see rather than give them instructions on unmapping the root directory and only mapping the ones they wanted to see. I tried it out and the feature works great. Thanks!
First at all, this is very nice and useful feature!!!!!
I'm using VS 2012 Ultimate edition.
I have some problems with it, may be U can help.
The scenario is like this:
1. Open Source control at first time when VS starts filters are working fine.
2. Close SC window (VS still runing)
3. Open again SC window, filters are not working, it's display all folders
I tried to click filter again, but no changes.
The solution is keep SC window open all the time, or close and reopen VS to re-enable that feature.
Do U have another way to force the filter working again?
Hi there, this extension definitely has some features I would like to use (especially the ability to hide cloaked folders), but I skipped 2012 to use 2013. Will you be making this available for 2013? Thanks!
Version for Visual Studio 2013 is separate package here http://visualstudiogallery.msdn.microsoft.com/af70cbb7-1e0d-4d16-bc57-cccc15370c51 or you can find it VS via Extensions and Updates Tools option.
Because in VS2012/2013 is no Pending changes window (Pending changes is part of the Team Explorer toolbox) I in VS2012/2013 Extension version placed Undo unchanged button to the Source Control Explorer window next to Workspace ComboBox.
I'm downloading to try this, and it looks useful, but in reading the documentation, I didn't see one thing that would be even more useful. Batch folder cloaking (or uncloaking). You can only cloak one folder at a time (and it seems to take forever on our remote TFS server). This is a pain on some poorly organized folders in our source where you regularly only want a few things in the folder. Be nice if it could be done simultaneously for multiple levels too...
1) In Source Control Explorer, right-click on something and choose the "Move to Folder" option provided by the extension.
2) In the dialog, click the Browse button
3) Hit cancel to dismiss all the dialogs
After the above steps, anything using the CTRL key doesn't work anymore (CTRL+Tab, CTRL+F, etc.) in Visual Studio 2012.
When exiting VS, you get a dialog with the following message:
Microsoft Visual Studio has detected that an operation is blocking user input. This can be caused by an active modal dialog or a task that needs to block user interaction. Would you like to shut down anyway?
I have read/write permissions to over 75+ projects in TFS but any one group in our development shop works on 1 or at most 3 at a time. Is there any way to "hide/remove/not see/filter" the ones I am not currently using in Source Control w/o messing with permissions in TFS?
I am using Visual Studio 2012 Shell (Integrated) with the Team Explorer and I can not install this awesome plugin (I tested it on another machine which has full VS2012 installed). Would you please mark the vsix (in the manifest) that it is compatible with the Integrated Shell (Team Explorer) Edition?
Would greatly appreciate this.