locked
Quick Find / Find in Files scope in Visual Studio 11 Beta

    Question

  • In Visual Studio 2008 and 2010, the "Quick Find" and "Find in Files" window had different search scopes. I was using the Quick Find window to search the current document and the find in files window to search the entire solution.

    In the new beta version, changing the scope in one window impacts the other window too. Is there a way to go back to the previous behaviour?

    Thank you

    Monday, March 12, 2012 3:06 PM

Answers

  • Hi Alex,

    Thank you for your suggestion.

    I suggest you to submit this suggestion to UserVoice , Microsoft engineers will evaluate them seriously, thanks.

    Best regards,

    Lucy


    Lucy Liu [MSFT]
    MSDN Community Support | Feedback to us

    Tuesday, April 10, 2012 7:00 AM

All replies

  • Hi Alex,

    In the VS11 Beta, we also can choose the scope,

    Please refer to the following photo: https://skydrive.live.com/#cid=475F7E3EBE2EEF90&id=475F7E3EBE2EEF90%21164



    Lucy Liu [MSFT]
    MSDN Community Support | Feedback to us

    Thursday, March 15, 2012 9:57 AM
  • If you change the scope in the Quick Find window (your screenshot) and then go in the "Find in Files" window, the scope will have changed too. I want to use different search scopes in the 2 windows, e.g. "Current document" in the Quick Find window and "Entire Solution" in the Find in Files window. This was possible in VS2005/2008/2010 but it looks like the 2 search scopes are now bound to the same preference in VS11 Beta.

    Thursday, March 15, 2012 11:57 AM
  • I have the same issue, hopefully it will be fixed before release.
    Wednesday, April 04, 2012 9:02 PM
  • Hi Alex,

    Thank you for your suggestion.

    I suggest you to submit this suggestion to UserVoice , Microsoft engineers will evaluate them seriously, thanks.

    Best regards,

    Lucy


    Lucy Liu [MSFT]
    MSDN Community Support | Feedback to us

    Tuesday, April 10, 2012 7:00 AM
  • It's really important to me. I tried VS11 for a short time then i switched back to the VS2010 only for this reason. I hope they'll fix it.

    Edit:

    I found a temporary fix extension for this (VS11 BETA ONLY Find Settings Seperator):  http://blogs.msdn.com/b/visualstudio/archive/2012/04/11/improving-find-amp-replace-in-visual-studio-11-beta.aspx

    • Edited by Mustafa SADEDIL Wednesday, April 18, 2012 2:57 PM found solution
    Wednesday, April 18, 2012 10:58 AM