Nice idea, but it would be great if the find window where dockable, and if you could associate a keyboard shortcut and command to it. I had to find all xsd files in the whole solution and it was a pain to navigate each time to open the find files dialog and loosing the selected item.
I could make it dockable, I opted not to in the end because I value real estate for the other aspects of Visual Studio.
You can assign a keyboard shortcut to it (Edit.VSFileNav) is the command to search for, which means you can include toolbar shortcuts too. The dialog should also remember the previous selection and search terms when you pop it up again.
I was looking for this feature for a long time. It even becomes more powerful when attaching a hot-key to it (through tools|options|environment|keyboard). With a few enhancement (see suggestions) it will be an A+ extension.
The extension runs correctly with VS2012, but you have to modify the VSIX file manually to make it install with VS2012 (http://researchaholic.com/2012/10/04/manually-updating-a-vsix-file-to-run-in-visual-studio-2012/).
I am however currently working on an update which will directly install to VS2012 and also have the following improvements which I'm hoping to release soon.
Thanks for this extension. I've been looking for this feature which resembles TextMate on iMAC 'Command+T"). I have two suggestions (copied from TextMate):
- Double click on the file in the list opens it
- Expand the search to look in names even when the typed in characters are not contiguous in the file name. Example: I have two files calles "EditorExtension.cs" and "EditorFragments.xml". Suppose I want to look for one of them but remember only the first part of the file and know which extension I'm looking for. So, entering "editorxml" locates the second file, while "editor" finds both.
These are very useful feature for keyboard hooked developers who prefer using the keyboard to the mouse.
@katrash: I'll add double clicking to open to my list (have some scrolling issues to fix too when the datagrid doesn't have focus).
For your example, use "editor*xml" and it'll bring up the result you're after. I didn't want to add in anything like this by default, as if you have lots of similarly named files you can end up with too many results, it's better if the user explicitly says this is what they want by simply inserting a *.
The minor things that can improve user experience a lot:
* documentation - add information about Edit.VsFileNav command;
* interface - why buttons aren't consistent with current windows theme? I use the classic one;
* interface - save windows size on closing;
* interface - pagedn/pageup/home/end not working.
Sergey, Thanks for the suggestions. I wrote a bit on my block to introduce it a bit better http://wrightdev.wordpress.com/2012/05/30/visual-studio-file-navigation-extension. You're right about the other suggestions, I should try and incorporate some of those. I'm thinking of releasing it as open source at some point as I never have to update it.
I'm glad you find it useful. I don't actually have VS2012 installed on my main Dev machine so I'm not able to upgrade it at this time. It also isn't currently open source but I'd be happy to make it open source if someone else would be willing to upgrade it. Unfortunately I don't spend much time working on it, as I never managed to achieve my original goal with it (e.g. Symbol Searching in a perfomant way) so it feels like a little bit of a failed project, even though what it currently does it does quite well. I'll look at moving it to some open source hosting over the next few weeks if I can and posting a link up here.