This project has moved. For the latest updates, please go here.
1

Closed

Ctrl+F or Advanced Find/Replace doesn't show anymore

description

No clue why this extension would interfere with it, but Ctrl+F (advanced find) doesn't work when the extension is enabled.

file attachments

Closed May 30, 2014 at 9:21 PM by davedev
Can't repro. Problem worked itself out.

comments

davedev wrote May 29, 2014 at 9:29 PM

Thanks for reporting it; however, I can't repro. I have it installed in VS 2013 and VS 2012 and Ctrl+F works fine for me in both.

With this extension enabled, have you tried switching to a different VS settings file? I only ask because key commands are also stored in the settings files, so perhaps you've simply chosen settings that disable that command (although I have no idea why you'd have a settings file without Ctrl+F mapped properly.)

Does simply disabling this extension alone fix the problem?
Does re-enabling this extension cause the problem to happen again?

If so, then try disabling this extension, export a settings file using the standard command on the Tools menu, re-enable this extension, and select the settings file that you just exported to active it. Does the problem still occur?

wrote May 30, 2014 at 12:27 PM

futureguis wrote May 30, 2014 at 12:27 PM

Yep simply toggling the extension makes it work and not work.

It almost seems like VS loses where it should put the dialog. If I have it docked it will work when I open a solution.

I've attached my settings file if that helps, but it only has text editor settings in it, so this is pretty weird.

davedev wrote May 30, 2014 at 1:39 PM

Ok, can you try my other recommendation? Here it is again:
Try disabling this extension, export a settings file using the standard command on the Tools menu, re-enable this extension, and select the settings file that you just exported to activate it.
Window positions are also typically stored in settings files, so I wonder if this will fix your problem.

In the meantime, I'll take a look at your attachment.

Thanks,
Dave

davedev wrote May 30, 2014 at 1:51 PM

I agree, the attached settings file doesn't seem like it's related to the problem at all. It's only a partial settings file.

When you install or enable this extension it automatically exports the current settings into an OriginalSettings.vssettings file , which is complete, and then it's applied. So I wonder if that file contains the settings that are causing you problems. Could you attach it? (I'll delete the attachment after I download it, if you'd like.)

davedev wrote May 30, 2014 at 1:58 PM

Also, could you see if the Ctrl+F command is mapped while the extension is enabled?
  • Go to Tools > Options > Environment / Keyboard
  • In the empty text box above the command list, enter "Edit.Find" without quotes.
  • Select Edit.Find in the list of commands (if it's not already selected).
  • The Shortcuts for selected command setting should be something like Ctrl+F (Global).
  • Select Edit.FindInFiles in the list of commands.
  • The Shortcuts for selected command setting should be something like Ctrl+Shift+F (Global).
    Can you confirm this is what you see while Ctrl+F doesn't work?

futureguis wrote May 30, 2014 at 6:11 PM

yeah, no clue what happened, but I've messed with the settings so much I can't reduplicate it anymore. If it happens again, or with other coworkers, I'll try to look into the keyboard mappings etc.

davedev wrote May 30, 2014 at 9:19 PM

Well I'm glad it works for you now. Thanks for taking the time to report the problem.

I'm going to close this work item. If the problem happens again, and you can get more information to help me debug it, then we can always reopen it.

For now I'm just going to assume that the problem was related to the typical strangeness that sometimes happens when switching between various Visual Studio settings/configurations, which is obviously beyond my control.

wrote May 30, 2014 at 9:21 PM

scottyhoag wrote Sep 2, 2016 at 12:53 AM

I know this issue has long since been closed for "working itself out", but it does seem to still exist. I'm using VS Community 2015 on Windows 10. Installing the extension causes both the "Find in Files" GUI icon and shortcut (Default: Ctrl+Shift+F) to stop working. Uninstalling the extension fixes the issue. The normal Find popup (Ctrl+F) is not affected by the extension. If anyone knows what settings they've changed around to fix this issue, sharing that knowledge would be appreciated. Thanks!

allender wrote Dec 5, 2016 at 3:18 PM

I had the same problem. I wound up using the "export current settings" command in the settings switcher toolbar. After that, I loaded up those settings, restarted VS, and find-in-file was working just fine. And it was working just fine using other per-solution settings that I had stored.