Hi Reviewers. In case you weren't aware, the Navigate To feature was included in the core Visual Studio product from Visual Studio 2013 onwards. You can access it in the same way via Ctrl+, or Edit...Navigate To. Take a look and let me know what you think by dropping me a line at mwthomas at Microsoft dot com . We continue to look at ways we can improve the feature in future releases. Thanks! Mark Wilson-Thomas, PM, VS Editor Team
Include in the next update of VS, please!!! :) Very useful!! I´m a Technical Educator for Windows Internals and C++ (always using VC++), and I have to create groups of blocks of code to my samples and this kind of tool helps a lot.
Roger Villela Technical Educator for Windows Internals and C++.
I screwed some of the settings in my VS2012 and "Navigate To..." option was not working even after resetting the whole settings.
Whenever I was hitting "CTRL+," I used to get "Entry point not found error". The only option left was to repair it via control panel or re install VS2012. Then one day during search I came across this extension.
Frankly, I doubted whether this will fix my issue, but it not only resolved my issue but enhanced the experience of searching a file in VS2012.
This tool is Awesome! Thanks!
One small thing, could you please fix a minor issue that I have observed when search box and navigate box comes together. many a time it looks clustered.
I would love to have it search for symbols in the current file only. It would be great if I can do something like:
where ! means current file (I just picked an identifier, doesn't matter what it is!) and foo() is a function in the current file. This will make it similar to Visual Assist where its "List and search methods" drop-down list is an extremely fast way of navigating your current file.
After little bit more thought, it would be great if there is a 'within current file' modifier. For example:
Great extension. Can you provide the option to Navigate to current File Member. Currently it looks for the entered keyword everywhere but many times developer wants to navigate to the method/property/fields of the current file.
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
Hi, I have vs2013 update 2 installed and during installation of the extension I get this.
4/6/2015 3:15:19 PM - Found installed product - Global Location
4/6/2015 3:15:19 PM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
This is an awesome tool, it reminds me of SublimeText's fuzzy searching with some of the symbol filters "@", ":".
Would it be possible to configure a setting where "@" constrains itself to the current open file?
I'm using VS 2013 Preview, and it purports to have this extension built in, with a similar dialog for "ctrl+,", but it doesn't look like I can use the special filters (":" for line numbers, etc). Do you know if these features were intentionally left out, or am I doing something wrong?
We didn't get around to having the filters put in place - we are looking to build a more extensible system (with an example) so people can build their own filters, but that's still in the planning phases -
I'll check if its easy porting the prototype to the new VS 2013, at least that way you can keep using it.
I'm using this, and I love it, but with larger solutions it starts to bog down and take a couple of seconds to return results.
Are there any plans to make the search indexed so it returns instantly? Or can you release the current code so others can add indexing?
I code with my monitor in portrait mode. I can see about an inch of the inline popup on the far right side of the screen, and the rest of it is offscreen. If I change my monitor landscape mode I can see the entire inline popup on the far right side of the screen.
Basically, the plugin needs to check to see what the bounds of the current monitor are, and it should always be rendered in a location so that the entire plugin is visible. This plugin is essentially unusable for me. I would actually prefer if the plugin location matched that of the built-in inline navigate to in Visual Studio 2013. There it is set up so that it always shows up just under the navigation drop down list at the top right of the screen rather than the far right side of the current highlighted line.
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?
I use Inline Navigate To at work and love it. I tried to install it in Visual Studio 2012 Express Web Edition Update 3 at home but found it not to be supported on that edition of Visual Studio.
Is the extension not supported in the Express editions at all? If not, can you please consider doing so!