All Open Documents Option in Find/Repace Dialog Does not work for SQL documents (Database Projects) - by ArthurZ

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 774024 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 12/11/2012 6:57:01 AM
Access Restriction Public


I came across this issue trying a new Visual Studio extension from the Visual Studio Gallery - Sync Block Edit at 
It turned out after communicating with the developer - the global text replace functionality for 'All Open Documents' option does not work for SQL documents in a Database Project.
I think this is rather a shortcoming that needs to be rectified.
Sign in to post a comment.
Posted by E4CH on 4/26/2016 at 1:18 AM
Please merge with this duplicate (two links, same feedback):
Posted by Doug Sipfle on 3/3/2016 at 4:05 PM
It doesn't make sense that this was closed as "By Design". If I open 10 of 200 sql files in my project and search across "All Open Documents" I would expect it to search those files. (...I just spent an hour trying to figure out if my version of Visual Studio 2013 had been corrupted by recent updates.)
Posted by Microsoft on 2/20/2013 at 1:27 PM
We do appreciate the report, but after evaluating the scope and impact of this issue, we have decided not to fix it.

thanks - Erick
Posted by ArthurZ on 1/3/2013 at 7:05 AM
thank you for looking into this.
I was using the Find control to set the scope explicitly.
Posted by Microsoft on 1/2/2013 at 7:10 AM

Thank you for logging the issue. Could you provide us more details on how you were trying to use the All Open Document scope ? Were you using the DTE or were you trying to set to scope explicitly using the Find control or the Find in files dialog ?

Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team
Posted by Microsoft on 12/11/2012 at 9:50 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 12/11/2012 at 7:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(