I really like this extension. I have some suggestions though.
- You should be able to write SomeComCWLN and get SomComplexClassWithLongName, but also SomeLonN and also get this class (but if there is a better match it should be first). Now only SCCWLN will work.
-the possibility to "narrow" results by providing other terms after space. For example, right now I can write "Index.cshtml" and get list of all Views files for Index action. If I only want views from HomeController I can write "index.c home" and narrow result to Index.cshtml from HomeController because files are matched also against path (and it matched "..\MyProject\View\Home\" path) It would be helpful if I could write "Create HoCo" and get all method that have "create" in name but from classes that would match HoCo pattern (HomeController for example)
-possibility to tell that files from particular folder name should be excluded from Navigate To results. For example it would be useful to exclude "T4" folder from T4MVC library so it won't clutter results (every action name is duplicated) Or maybe provide an option so files that have "// <auto-generated />" comment at beginning won't be considered in results.
If we get enough votes, it'll help us prioritize this over other things. Share it around
As a DarkTheme user that doesn't like modal dialogs i'm quite happy to see a replacement for the NavigateTo dialog that integrates much better into the new VisualStudio UI.
For now it seems to work quite well. With some further improvements it would be an excellent extension with 5 stars, till then 4.
My suggestions: 1.) Enable more filter options: Class, Property, Field, Method... 2.) Add an option to disable that the editor view automatically opens the item highlighted in the InlineNavigation list. In my opinion this behavior is quite annoying. If disabled e.g. space bar should open in editor view but leave InlineNavigation active, enter opens item in editor view and closes the inline navigation. 3.) Add the possiblity to also set the filter at the end of the search term. Often i search for something and when there are too many results I then want to apply an filter. So '~Something' and 'Something~' should deliver the same results.
Agree with previous review re: an option to disable previewing/opening auto-highlighted or single-clicked files in the Navigate To window. I've turned off Preview Tab in my main VS options and now auto-highlighted or single-clicked files in the Navigate To window are opened in full-edit mode, which is even more inconvenient than a preview tab.
First, I love this extension - thanks!
I accidentally reset my keyboard bindings back to the default, and now CTRL+, opens the default navigate to dialog. I (un)(re)installed the extensions, but I can't get the keyboard hook to come back. Any ideas?
The idea to combine few navigation dialogs into one is good and implemented well.
I would like to see it merged with Find/Find in Files/Search Solution Explorer. It's great to have single point of navigation with consistent experience.
I like it, really do, it fits in nicely with the new Find/Replace dialog and the dark theme. As some of the other reviewers have mentioned, it'd be great if it supported camel case search and scoping to the current project or file.
The biggest problem I'm having is that it never receives focus when it opens - the focus just stays inside the editor and I have to manually click on the window before I can start typing. I've tried disabling my other extensions, as well as reinstalling this one, but the problem persists. If anybody has any suggestions, I'd appreciate the help.
Hmm, that sounds like it will be tricky to diagnose without some debugging. Besides things you've already tried (disabling extensions), does the problem happen even if, say, the Solution Explorer has focus when you execute the command?
Also, I'll just point out that the camel-case behavior is the same as the original Navigate To dialog (because this one uses the same source of data). C# and VB class/member search was written to support camel-case, but file names and C++ types were not. That's definitely something we'd like to make consistent, but it's more invasive to fix since that logic is built into other Visual Studio components that this extension relies on.
I've just tried it from several different places and the results are never what you'd expect. The focus stays where it is whenever I launch the search from the text editor (be it code, xml, xaml, config, etc.), Solution Explorer, Performance Explorer, Test Explorer, SQL Server Object Explorer, or the search field of the Toolbox.
When the focus is on an item in the Toolbox, an item in a Class Diagram, or the Project Properties designer, the focus seems to disappear (it doesn't move to the window, but at the same time it doesn't stay where it was). Despite not having focus, the window can always be dismissed by pressing escape, but the focus stays in the mystery location until I press escape a second time, at which point it returns to where it was before the search was opened.
When I have more free time, I'll try disabling everything again, it might just be something I missed. I'll also get a few people around the office to try it out and see if any of them have similar issues.
Anyway, thanks for the reply, and keep up the great work.
I really like CamelCase searching in the old Ctrl+, dialog, searching SBL for ServerBeginLogon for example. That doesn't seem to work for file names.
Also, it would be nice to limit the simbol search to current file/project, I have biiiig solutions and searching for a symbol gets pretty complicated when we got many projects with similar simbol names.