VS 2010 Find<\/strong><\/p>\n<\/td>\n Power Tools Find<\/strong><\/p>\n<\/td>\n<\/tr>\n Pressing Ctrl+F will invoke the extension\u2019s Quick Find.\u00a0 Incremental Search users will also notice that Ctrl+F and Ctrl+I are one and the same \u2013 our hope is that the extension is fast and light enough to replace the built-in Incremental Search.\u00a0 The UI should always sit in the upper right corner of the editor and includes, from left to right:\u00a0 toggle to switch to Replace, Find What box, Find Previous button, Find Next button, and Close button.\u00a0 It looks like this:<\/p>\n Pressing Ctrl+H will invoke the extension\u2019s Quick Replace.\u00a0 Its UI has everything from Find plus a Replace With box, Replace Next button, and Replace All button.\u00a0 It looks like this:<\/p>\n Results are found incrementally and all matches are highlighted almost instantaneously in the editor.\u00a0 The default highlight color is yellow and is customizable through Tools->Options->Environment->Fonts and Colors->Find Highlight (Extension).\u00a0 The Enhanced Scrollbar extension, also new in this power tools release, also displays markers that show where all of the results are in your file.\u00a0 These are orange by default and customizable through Tools->Options->Productivity Power Tools->Enhanced Scroll Bar->Find results color.<\/p>\n The Quick Find extension also includes a search history and common options in the Find What dropdown box:<\/p>\n The \u201cUse Regular Expression\u201d option has also received a long-awaited update:\u00a0 it now uses .NET regular expressions!\u00a0 This is one of the most common requests we receive for the Find dialog, so we\u2019ve added it to the extension\u2019s Quick Find.\u00a0 We are also hoping to update the regular expressions in the built-in Find in Files dialog; that part is much harder to do via extensibility and is not available yet, but it is on our to-do list.<\/p>\n Clicking \u201cAdvanced Options\u2026\u201d or pressing Ctrl+Shift+F will take you to the built-in Find in Files dialog.\u00a0 To reach the built-in Quick Find, just go to Find in Files and press Ctrl+F.\u00a0 Similarly, you can reach Replace in Files with Ctrl+Shift+H and Quick Replace with Ctrl+Shift+H, Ctrl+H.<\/p>\n Last but definitely not least, there is a \u201cSend Feedback\u2026\u201d link at the bottom of the Find What dropdown.\u00a0 This allows you to directly e-mail the team that built this extension, including the developer, tester, and program manager.\u00a0 We read every e-mail and are already planning an update to the extension based on your feedback.\u00a0 We would love to hear from you!<\/p>\n Based on your feedback and our bug backlog and \u2019wish list\u2019 of mini-features to add, we\u2019re planning an update to the Find extension in the next Pro Power Tools release.\u00a0 This is not an exhaustive list and not all of these will make it into the very next version, but we\u2019ve highlighted the top issues we hope to address.<\/p>\n By far the #1 piece of extension feedback so far is about scope.\u00a0 The current version of the extension always uses the current document or window as its scope, but you can still do a find in selection, current project, entire solution, etc. by going to Find in Files (Ctrl+Shift+F) or, for selection and current block, the built-in Quick Find (Ctrl+Shift+F, Ctrl+F).\u00a0 We have heard loud and clear that being able to search in other scopes is critical and we\u2019ll be working that into Quick Find in the next Pro Power Tools update (release date still TBD \u2013 watch this blog for news!).<\/p>\n We also knew when we released this extension that its keyboard support is not yet complete, and that\u2019s something we plan to address.\u00a0 This includes:<\/p>\n After you\u2019ve done a search, we plan to add an overlay that says \u201cx of y\u201d (but with numbers), where x is your current match and y is the total number of matches.\u00a0 This should also make it clearer when there are no matches and when your search passes the end of your document.<\/p>\n We\u2019re prioritizing our idea list and adding new suggestions to that list based on your feedback, so we would love to hear from you!\u00a0 Positive and negative comments, mini-feature suggestions and bug reports, and any other thoughts you have are more than welcome.\u00a0 And if you choose to disable the extension (Tools->Options->Productivity Power Tools->All Extensions), we would ask that you send us a quick e-mail so we know why and can hopefully address your concerns in a future version.\u00a0 Just use the \u201cSend Feedback\u201d link in the Find dropdown or contact us directly at VsFindFeedback@microsoft.com<\/a>.<\/p>\n Enjoy!<\/p>\n Brittany Behrens\nProgram Manager, Visual Studio Editor team & Quick Find extension<\/p>\n","protected":false},"excerpt":{"rendered":" We\u2019re pleased to announce a new Quick Find (Ctrl+F) extension in the February release of the Productivity Power Tools.\u00a0 This is the first version of the Quick Find extension and we are planning to make some improvements to it in future Power Tools releases, but this blog post describes the reasons for the extension, its […]<\/p>\n","protected":false},"author":13,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[294,526,13],"class_list":["post-1623","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-extensions","tag-productivity","tag-visual-studio-2010"],"acf":[],"blog_post_summary":" We\u2019re pleased to announce a new Quick Find (Ctrl+F) extension in the February release of the Productivity Power Tools.\u00a0 This is the first version of the Quick Find extension and we are planning to make some improvements to it in future Power Tools releases, but this blog post describes the reasons for the extension, its […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/1623","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=1623"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/1623\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=1623"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=1623"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=1623"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n \n Covers too much code<\/td>\n Occupies very little space<\/td>\n<\/tr>\n \n Jumps around during searches<\/td>\n Remains stationary<\/td>\n<\/tr>\n \n No immediate results<\/td>\n Uses an incremental search for nearly instant results<\/td>\n<\/tr>\n \n Uses outdated regular expression syntax<\/td>\n Uses familiar .NET regular expression syntax<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n What can it do today?<\/h2>\n
Basic Quick Find\/Replace<\/h4>\n
![\"Quick](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2011\/03\/5584.image_thumb_5CF15F72.png\" "\\"Quick")
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nFind History and Options<\/h4>\n
<\/a><\/p>\nWhere is the extension going in the future?<\/h2>\n
Find in more scopes<\/h4>\n
More complete keyboard support<\/h4>\n
\n
Number of Matches<\/h4>\n
Send us feedback!<\/h2>\n