ipwright83/vsfilenav

Visual Studio extension for rapid finding of files within a solution

vsfilenav's Issues

Visual Artifact on a Row

On the end of each row in the Dark theme there is a visual artifact.

Double Border

On the Light and Blue themes there's a double border affect we can see:

Space as wildcard

Having space as a wildcard (like sonic file finder) is awesome. Makes finding things much faster. Even better would be fuzzy matching where you kind of infer a wildcard between each character, but sort by files with matching adjacent characters first.

I can't find the license information.

I cannot find any license information that applies to this software.
(e.g. MIT License/Apache License...)

120 DPI

It's been reported that the extension doesn't play nicely with 120 DPI mode. In fact text scaling might be an overall issue, especially with higher DPI monitors being introduced.

Page Up / Page Down

These keys don't seem to scroll the list but they should do.

Culture based string searching

Transcript from:

https://visualstudiogallery.msdn.microsoft.com/cfdf85c2-aaa4-4bdd-b8ea-e22bcc9860af/view/Discussions

**AlexanderMDk**
Hello, very nice extension. I have one issue though: When I type "ac" to search for a file named ActivityFactory.cs, the dialog simply closes the instant I type the "c". This only happens in a certain solution (with around 20 projects, thousands of files). In another solution, where the ActivityFactory.cs file is also present, it works fine. Is there any way to debug this?

**CdTC**
Hi IPWright83, I found that bug AlexanderMDk mentioned.
It's in the StringMatch.cs file and public StringMatch(String fullString, String matchString) function.
Here you have this code:

int startIndex = fullString.ToLower().IndexOf(matchString.ToLower());
...
this.Parts.Add(new StringPart(fullString.Substring(startIndex, length), true));

**CdTC**
And its probably bug int the C# IndexOf(string) implementation.
Because for:
string fullString = "CharSets.hxx";
string matchString = "c";
int startIndex = fullString.ToLower().IndexOf(matchString.ToLower());

returns -1 in Visual Studio 2015. When I changed string matchString to CHAR matchString then it returned 0 as it should.

**CdTC**
ok, sorry for spam and previous useless post, but I found the reason.
IndexOf is CULTURE sensitive so here in Czech Republic we have c, h and ch letters = CharSets.hxx string looks like "Ch|a|r|S|e|t|s|.|h|x|x".

I dont know the best solution for fixing this, but this works for me:
int startIndex = fullString.ToLower().IndexOf(matchString.ToLower(), StringComparison.Ordinal);
or less verbose
int startIndex = fullString.IndexOf(matchString, StringComparison.OrdinalIgnoreCase);

**AlexanderMDk**
Thanks for the fix CdTC, glad I'm not the only one. I tried making the edit in the source code, but I don't know how to build and "deploy" the extension. If I go to the output directory and double-click the VSNav.vsix file, it spins for a few seconds, then complains the extension is not signed (even though it is using the Key.snk file included in the project). Can the author do us a big favour and update the code with the change CdTC suggested? Thanks

Space as OR splitter

It would be useful to have the space character default to splitting the search into multiple terms, any of which can be present in the searched file name:
e.g: Searching for "complex name" would find "mycomplexname.cpp", "mysimplename.cpp", "mycomplexandlongname.cpp", "anamethatiscomplexandlong.cpp" and "my complex name.cpp"

This effectively extends the "Space as a wildcard" issue by not enforcing ordering in the searched strings.

Visual Studio 2017 support?

Any chance of updating this extension to support Visual Studio 2017? I'm on day one of using VS 2017 and I already miss VSFileNav like crazy!

I tried using the existing installer from https://marketplace.visualstudio.com/items?itemName=IPWright83.VSFileNav-17743, but the VSIX installer reported "This extension is already installed to all applicable products."

Thanks! (Let me know if I can do anything to help!)

Installation failed for unkown reason with VS 2013

For unkown reason I cannot installe the plugin in VS 2013 Update 4
This is the log, any suggestion what to do?

12.01.2017 14:57:40 - Microsoft VSIX Installer
12.01.2017 14:57:40 - -------------------------------------------
12.01.2017 14:57:40 - Initializing Install...
12.01.2017 14:57:40 - Extension Details...
12.01.2017 14:57:40 - 	Identifier      : d1fa1e4a-6cb3-42cd-9141-787813a57c02
12.01.2017 14:57:40 - 	Name            : VSNav
12.01.2017 14:57:40 - 	Author          : Ian Wright
12.01.2017 14:57:40 - 	Version         : 15.1
12.01.2017 14:57:40 - 	Description     : This is a simple extention to allow rapid navigation and finding of files within a Solution using a number of different search patterns.

For more information please visit https://github.com/IPWright83/VSFileNav
    
12.01.2017 14:57:40 - 	Locale          : en-US
12.01.2017 14:57:40 - 	MoreInfoURL     : https://github.com/IPWright83/VSFileNav
12.01.2017 14:57:40 - 	InstalledByMSI  : False
12.01.2017 14:57:40 - 	SupportedFrameworkVersionRange : [4.5]
12.01.2017 14:57:40 - 
12.01.2017 14:57:40 - 	Supported Products : 
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.Pro
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.Ultimate
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.Premium
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.VSWinExpress
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.VSWinExpress
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.VPDExpress
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.VWDExpress
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.VWDExpress
12.01.2017 14:57:40 - 			Version : [14.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.IntegratedShell
12.01.2017 14:57:40 - 			Version : [14.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.Community
12.01.2017 14:57:40 - 			Version : [14.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.VSWinDesktopExpress
12.01.2017 14:57:40 - 			Version : [14.0,16.0)
12.01.2017 14:57:40 - 		Microsoft.VisualStudio.Enterprise
12.01.2017 14:57:40 - 			Version : [11.0,16.0)
12.01.2017 14:57:40 - 
12.01.2017 14:57:40 - 	References      : 
12.01.2017 14:57:40 - 		-------------------------------------------------------
12.01.2017 14:57:40 - 		Identifier   : Microsoft.VisualStudio.MPF.11.0
12.01.2017 14:57:40 - 		Name         : Visual Studio MPF 11.0
12.01.2017 14:57:40 - 		Version      : [11.0]
12.01.2017 14:57:40 - 		MoreInfoURL  : 
12.01.2017 14:57:40 - 		Nested       : No
12.01.2017 14:57:40 - 
12.01.2017 14:57:40 - 
12.01.2017 14:57:40 - Searching for applicable products...
12.01.2017 14:57:40 - Found installed product - Microsoft Visual Studio Professional 2013
12.01.2017 14:57:41 - The extension with ID 'd1fa1e4a-6cb3-42cd-9141-787813a57c02' is not installed to Microsoft Visual Studio Professional 2013.
12.01.2017 14:57:41 - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated)
12.01.2017 14:57:41 - Found installed product - Global Location
12.01.2017 14:57:43 - The following target products have been selected...
12.01.2017 14:57:43 - 	Microsoft Visual Studio Professional 2013
12.01.2017 14:57:43 - 
12.01.2017 14:57:43 - Beginning to install extension to Microsoft Visual Studio Professional 2013...
12.01.2017 14:57:43 - Install Error : Microsoft.VisualStudio.ExtensionManager.MissingTargetFrameworkException: The extension 'VSNav' requires a version of the .NET Framework that is not installed.
   bei Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForValidDotNetFramework(IExtension extension)
   bei Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForInstallBlockers(InstallableExtensionImpl extension, IInstalledExtensionList modifiedInstalledExtensionsList, Boolean isNestedExtension, Boolean& olderVersionInstalled)
   bei Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallInternal(InstallableExtensionImpl extension, Boolean perMachine, Boolean isNestedExtension, IDictionary`2 extensionsInstalledSoFar, List`1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, UInt64 totalBytesToWrite, UInt64& totalBytesWritten)
   bei Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)
   bei Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)

I have installed .net Framework 4.6.2

The extension doesn't work in VS2017 if some features aren't installed

I used to use the extension with VS2017 - it had been working fine a couple of releases ago.
However after I installed the version 15.5.2 of Visual Studio Community 2017 (Microsoft Visual Studio 2017 version: 15.0.27130.2010) on the new PC, I'm not able to use VSFileNav any more.
The error is:

The 'VSNavPackage' package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'E:\Users\Anton\AppData\Roaming\Microsoft\VisualStudio\15.0_91a35b65\ActivityLog.xml'.
Restarting Visual Studio could help resolve this issue.

The errors in the XML-log are:

LegacySitePackage failed for package [VSNavPackage]Source: 'EnvDTE' Description: Неизвестное имя. (Exception from HRESULT: 0x80020006 (DISP_E_UNKNOWNNAME)) System.Runtime.InteropServices.COMException (0x80020006): Неизвестное имя. (Exception from HRESULT: 0x80020006 (DISP_E_UNKNOWNNAME)) at EnvDTE.Events.GetObject(String Name) at VSNav.EventManager.GetDTE() at VSNav.VSNavPackage.Initialize() at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
SetSite failed for package VSNavPackage

Scroll Bar Colour

When using the Dark Theme, the default light scroll bars don't look very nice.

Remember Window position

The dialog doesn't remember it's position when you close/re-open it which some people would like fixed.

Images!

Class Searching

It would be really nice to be able to search for a class (rather than a file name) in the solution.

Compatibility with VS 2015

Hello,

Could you make it compatible with VS 2015 please?

Thanks

Req: removing duplicates

Hey, totally awesome extension, looks like something that you just can't live without :)
I have only one request - because using shared project in a big solution with lots of projects using files from that shared project (the file is single copy, but used around) so as a result every file is shown like 10 times in the list cluttering the display and making hard to actually select the file without pretty much typing the whole name. Visual Studio 2017 here.

Fix the manifest

I'd like to be able to host just a single copy of the VSIX installer on the Visual Studio Gallery - I need to sort out the issues with the manifest file to do this such that it's future version compatible.

Probably need some willing volunteers with VS2012/VS2013 copies to test this.

Update Readme

Should update the ReadMe to make it clearer on the usage examples and how to apply key re-bindings.

Any license on this?

I just wonder as I am trying to kill my use of resharper as it kills Visual studio (Heavy on ram usage) but I miss the Goto.FileMember which resharper has, and it could be bulid much like this extension, it should just look in just the currently opened file and search for member names.

So any license that prevents me from trying to fork this and create that (Not done any extensions before though)

embed in VS window

Seems like this extension is pretty much exactly what I am looking for. However it would be more convenient to leave it open embedded in one of the VS areas, perhaps as a tab next to the "output" window for example. Unfortunately it doesn't seem to support being embedded in the VS window at the moment. Can it be fixed?