Visual Studio 11 - Text Search scope is shared between Quick Find and Find in Files by gucorgnet

We have a new version of the Settings separator extension that now works on Visual Studio Beta update builds as well. 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.
New Download link: 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

Hello,
Thank you for logging this issue. This has been one of the top reported bugs and we are addressing it post-Beta. In the meantime, we have an extension (link below) that should work around the issue so you can work with separate scope and search options.
Download: VS11_Beta_Only_FindSettingsSeparator.vsix
(http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-29-92/3683.VS11_5F00_Beta_5F00_Only_5F00_FindSettingsSeparator.vsix)

IMPORTANT: The extension provides a workaround for the shared scope & options issue. Please note that this extension can be expected to work correctly only on Beta and should be uninstalled when upgrading to future versions. This extension will not be serviced by Microsoft. If you encounter any issues after installing the extension, please uninstall and restart Visual Studio.

We invite you to visit the Find Blog post on Beta (http://blogs.msdn.com/b/visualstudio/archive/2012/04/11/improving-find-amp-replace-in-visual-studio-11-beta.aspx)

Thanks,
Murali
Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team

Hello,

Thank you for logging this issue. Sharing settings between Quick Find and Find-in-files is definitely an issue. These settings should be separate. We agree with you, and this has already been fixed in internal builds. We just couldn’t get it time for Beta. You should get the correct behavior in future versions. For Beta, we are planning to release an extension that works around this issue. Stay tuned on the Visual Studio Blog!

-Murali
Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team

Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)