Not very good. Thing I dislike most is the path shown is the fully qualified physical path of the file... so when you have your project several folders deep and you try to find a fairly commonly named file which appears in several locations (let's say default), the path column shows drive:\some\really\amazingly\long\path\to\your\file.txt and you have to expand the hell out of the path column to see which file they're talking about. If I have to do that, it's probably quicker just to navigate to the file location manually. File paths should key off of the solution root.
You also can only find files by typing part of the file name and only files are shown. Perhaps I don't know exactly what the file I'm looking for might be named, but I know the directory path in which it is located.. it is nice to be able to type /path/to/file and see a spit out of all the files in the specified directory and then I can quickly grab the file I'm looking for.
I don't know why this extension is called Quick Open File for Visual Studio 2010. This extension is very very very slow !!!! I have a project which heavily realies on boost and it includes about 20000 files ! In my case, the extension is unusable.
Good extension! Just a suggestion … It will be most useful if the text box gets focus and selects entire string every time after the popup is shown or activated. Now if I double click on a file to open it and then open the popup again, the focus is on the list box. That prevent me to type immediately and I have to go back to the text box.
Our solution contains approximatly 10,000 files which makes the searching a bit slow. As it is, the extension works very well but doesn't match Eclipse for speed in a large solution.
It might work better if I could type my search string without it refreshing the list on every character typed. Introducing a short timer (eg. 200 milliseconds) that gets cancelled if another character is typed before kicking off the search might make it appear more responsive.