Search

Option to 'Hide Find and Replace window...' is missing from Visual Studio 2012 by bukbukbukark

Closed
as Deferred Help for as Deferred

2
0
Sign in
to vote
Type: Bug
ID: 779182
Opened: 2/13/2013 5:51:37 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
Visual Studio 2012 is missing the option to 'Hide Find and Replace window after a match is located for Quick Find or Quick Replace'. This option was in Visual Studio 2008, under Environment / Find and Replace, and when turned on it immediately removes the Quick Find or Quick Replace window and returns focus to the editor (this was the default behavior in earlier versions of VS if I remember correctly).

In VS 2012 it seems you have no option but to manually return focus to the editor, which is clumsy and difficult to adjust to after using previous versions of Visual Studio for so long.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

Open Tools / Options / Environment / Find and Replace.

The option to Hide Find and Replace window after a match is located for Quick Find or Quick Replace is missing.

Product Language

English

Operating System

Windows 8

Operating System Language

English

Actual results

Open Tools / Options / Environment / Find and Replace.

The option to Hide Find and Replace window after a match is located for Quick Find or Quick Replace is missing.

Expected results

Open Tools / Options / Environment / Find and Replace.

The option to Hide Find and Replace window after a match is located for Quick Find or Quick Replace should be present.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/25/2013 at 7:28 AM
Hello,

Thank you for logging this issue. We will definitely consider fixing this issue for future versions. I am marking this bug as copied to our backlog. Please feel free to vote up this issue.

Thanks,
Murali
Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team
Posted by Microsoft on 2/13/2013 at 11:55 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 2/13/2013 at 6:52 PM
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)
Sign in to post a workaround.