16 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Anthony Steele commented  ·  February 22, 2013 6:31 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Totally agree.

  Today I did a search to find out why Find in Files (Ctrl+Shift+F) keeps showing the scope of "Current Document" which is an annoying, rubbish default for "in files". If I wanted "in current document" I would have pressed "Ctrl-F". Thanks for at least showing me why this is broken.

• Daver commented  ·  May 8, 2012 9:42 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It would be best if the Search Text box should be able to search for text strings, find in files, find all references or any combination of the above (checkboxes)!

• Dave commented  ·  April 16, 2012 12:19 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Thanks for the update Murali, I was wondering why the previous extension wasn't working. Note that I got an error stating that the new version is already installed. After uninstalling the old extension (Tools > Extension Manager > VS BETA ONLY Separator > Uninstall) and closing VS, then I was able to installl the new extension and it works great. This was a much-needed fix, thanks.

• AdminVisual Studio team (Product Team, Microsoft) commented  ·  April 16, 2012 8:58 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  For those of you who upgraded to VS Update, the extension would have installed, but not worked. This is because it was configured to strictly work only on Beta. Please download and install this new version and it should work for you. We have a new version of the Settings separator extension that now works on Visual Studio Beta update builds as well. The extension can be downloaded from the link below.
  http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-29-92/6746.VS11_5F00_BETA_5F00_ONLY_2D00_FindSettingsSeparator.vsix
  
  Thanks,
  Murali
  Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team

• Dave Novak commented  ·  April 12, 2012 4:26 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I was happy to see a fix come out so quickly for the shared scope bug, except the find settings separator patch DOES NOT WORK! Has anyone gotten this to work? It shows up as installed and enabled; it just doesn't solve the problem it was intended to fix. Both Find in Files and the Find Control STILL share the same scope even with this extension installed/enabled. I've even uninstalled/reinstalled this extension and still no luck. What a mess!

  Let me know when you guys have a fix for your "fix" available and I'll once again do your alpha testing. :(

• John Saunders commented  ·  April 11, 2012 11:48 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I totally disagree. In general, searching is searching.

  I like the idea of search scopes, but not this way. I may be searching for occurrences of "x", for each of which I'll start looking for the occurrences of "y". I'd like to have two "search containers", and be able to switch between them. This happened to me yesterday, when I wanted to find a set of stored procedures with "x", for each of which, I wanted to search for a set of columns ("y"). I wanted to try the narrowest search scope first (project and *.cs, *.sql), and then broaden it out. But I still wanted to switch between "x" and "y".

• Dave Novak commented  ·  April 10, 2012 7:49 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Totally agree! For example, if I use Ctrl+F to go to Find control, enter find text, and set the scope for Current Document, then Current Document becomes the scope for the Find in Files dialog. I think this is really bad and very different than the was this has worked for many years in previous versions of Visual Studio. In VS-2010, VS-2008, VS-2005, and I'm sure older versions, the scope for Find in Files dialog was always different than the scope for the Find dialog. And this is GOOD that they are different because they are used for different purposes.

  For example, in my use case above (going from Find control to Find in Files dialog), I will (most likely) need to change scope in Find in Files dialog to something like Entire Solution. Only then will I find the results I'm looking for. But what happens when I switch back to the Find control for the purpose of just searching the current document? Oops -- still searching the Entire Solution! I've found myself constantly having to change this scope, which is something I never had to do in previous versions of Visual Studio. It is SO ANNOYING!

  Please fix this! There should be 2 separate scopes: one for the Find Control and one for Find in Files.

• John West commented  ·  April 9, 2012 6:43 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  In fact, can I give all my votes to this one :)?

• John West commented  ·  April 9, 2012 6:43 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is my single biggest painpoint in vs2011, believe it or not. One day I'm not going to be deligent, and i'm going to do a replace across the entire solution instead of just the current file!

• yurik commented  ·  April 1, 2012 10:24 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  The only way around it until it gets fixed is to use Ctrl+F12 if you have Resharper - searches by method name in the file :)

• Philippe commented  ·  March 31, 2012 7:43 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Definitively a must. I generally use Ctrl+F to fin something in the current document and Ctrl+Shift+F to search in the whole solution. Same for Ctrl+H versus Ctrl+Shift+H.

• Alexander commented  ·  March 27, 2012 8:49 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  In most cases I use 'Quick Find' for finding in current document and 'Find In Files' for finding across all the documents. It makes me mad when 'Quick Find' starts finding across the whole solution (after 'Find In Files' was performed).

• Alexander Gonchar commented  ·  March 26, 2012 8:36 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  +100500 for this suggestion!

• Dave commented  ·  March 19, 2012 7:58 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'm voting on this request because it already has more votes than the following similar request:

  http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2667822-have-different-settings-from-find-in-files-and-qui

• Peter commented  ·  March 13, 2012 12:38 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Agreed. Also, the "Find in Files" dialog's "Look in..." dropdown doesn't respond to "ALT+DOWNARROW" like all other dropdowns in Windows, making it more difficult to perform a common "Find in all files" operation.

• Aaron Lieberman commented  ·  March 9, 2012 8:18 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Agreed. I almost exclusivly want to use quick find in my current document and find in files across multiple documents.