{"id":4173,"date":"2009-11-17T10:49:00","date_gmt":"2009-11-17T10:49:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/vcblog\/2009\/11\/17\/improvements-to-find-all-references-in-visual-studio-2010\/"},"modified":"2019-02-18T18:45:44","modified_gmt":"2019-02-18T18:45:44","slug":"improvements-to-find-all-references-in-visual-studio-2010","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/improvements-to-find-all-references-in-visual-studio-2010\/","title":{"rendered":"Improvements to Find all references in Visual Studio 2010"},"content":{"rendered":"

Hello, my name is Raman Sharma, and I am a Program Manager on the VC++ team.  Through this blog post, I wish to highlight some changes we have made to an important feature in the C++ IDE, called \u201cFind all References\u201d.  As most of you would know, this feature is used to search for references to any element of your code (classes, class members, functions etc.), inside the entire solution.  In Visual Studio 2010, we have made some changes to this feature to provide more flexibility.<\/font><\/p>\n

Let\u2019s look at these changes through an example.  Let\u2019s say you have the following piece of code:<\/font><\/p>\n

<\/p>\n

Figure 1: Sample Code<\/font><\/strong><\/p>\n

The Old World<\/font><\/font><\/font><\/span><\/h2>\n

In Visual Studio 2008, if you invoke \u201cFind all References\u201d on the member function <\/font>printArea<\/span> of class <\/font>Circle<\/span> as in:<\/font><\/font><\/p>\n

<\/p>\n

Figure 2: Invoke Find all References<\/font><\/strong><\/p>\n

You will see the results showing line numbers 7, 20 & 26 as below:<\/font><\/p>\n

<\/p>\n

Figure 3: Results in VS 2008<\/font><\/strong><\/p>\n

It is to be noted that the results window does not<\/b> list all the places the word \u201cprintArea\u201d appears.  It only lists specifically the places where printArea means the \u201cmember function <\/font>printArea<\/span> of class <\/font>Circle<\/span>\u201d (on which Find all References was invoked).  The point is that this is in some sense a compiler-verified-search (I just coined that term but the concept is correct<\/font>J<\/span>) wherein you will get exactly the C++ symbol you searched for.<\/font><\/font><\/p>\n

The New World<\/font><\/font><\/font><\/span><\/h2>\n

In Visual Studio 2010 we have effectively created two modes of search: one that focuses on speed and the other that focuses on accuracy.  Needless to say, you can specify the default mode through options and we will remember that setting.  More on that later in this post.<\/font><\/p>\n

Speed Mode<\/font><\/font><\/font><\/span><\/h3>\n

If you perform the same operation as described above in VS 2010, by default you will get the following results:<\/font><\/p>\n

<\/p>\n

Figure 4: Default results in VS 2010<\/font><\/strong><\/p>\n

Please note that this time around, the results window does<\/b> list all the places the word \u201cprintArea\u201d appears (including the comments!).  Why? Because we wanted to provide the user with an option to search without invoking the compiler.  Needless to say, this option will speed up the search significantly, especially for large projects with a lot of hits.<\/font><\/p>\n

It\u2019s worth mentioning that this search is unlike<\/b> just searching for some text in the entire solution.  This is because for this search, the C++ IDE uses an index to narrow the list of files to search.  So it doesn\u2019t look through all the files in the solution.  The outcome is significantly better performance than just \u201cFind in Files\u201d (or grep), especially for large solutions.<\/font><\/p>\n

Accuracy Mode<\/font><\/font><\/font><\/span><\/h3>\n

However, we understand that there can be instances where you want to reduce the ambiguity by filtering the results further.  This means you want better accuracy.  If you search for a member function of a class, you only want references to that member function of that class.  This is even if there are other classes with same named members or other overloads for this function within the same class.  To do this, right-click on the results in the results window and invoke \u201cResolve Results\u201d:<\/font><\/p>\n

<\/p>\n

Figure 5: Invoke Resolve Results<\/font><\/strong><\/p>\n

\u201cResolving results\u201d uses the compiler to actually verify\/confirm the entries and removes references that don\u2019t precisely match.  You will be presented with the following results which contain only exact references to <\/font>Circle::printArea<\/span>:<\/font><\/font><\/p>\n

<\/p>\n

Figure 6: Resolved results in VS 2010<\/font><\/strong><\/p>\n

If you are feeling more adventurous, there is another part of the accuracy mode which is like asking the following question to the compiler: \u201cFilter out as many extraneous results as you can, and for those you are not sure about, show them anyway\u201d<\/i>.  The reason you would want to ask that question is if you want comments, code in different macro states etc. to be included in the search results.<\/font><\/p>\n

The way to ask this question is to simply right-click on the resolved results in the window and to uncheck \u201cHide Unconfirmed\u201d:<\/font><\/p>\n

<\/p>\n

Figure 7: Uncheck “Hide Unconfirmed”<\/font><\/strong><\/p>\n

Doing this will make sure that search results will exclude only those results which the compiler has verified are definitely not<\/b> references of <\/font>Circle::printArea.<\/span> Anything that the compiler verifies is correct and anything it is not sure about will be listed.  The results will be as shown below:<\/font><\/font><\/p>\n

<\/p>\n

Figure 8: Resolved and Unconfirmed results in VS 2010<\/font><\/strong><\/p>\n

Notice this time the results include the comments.  It\u2019s worth mentioning that this is the only mode that was supported by VS 2008<\/font><\/p>\n

The default mode for search is the speed mode.  This means, when you invoke Find-all-References, you will see all the places your search item appears.  However as with everything else in Visual Studio, there is a way to change this default behavior.  If you go to \u201cTools -> Options -> Text Editor-> C\/C++ ->Advanced\u201d, under References you will find two new options \u201cDisable Resolving\u201d and \u201cHide Unconfirmed\u201d:<\/font><\/p>\n

<\/p>\n

Figure 9: Options to set default search mode<\/font><\/strong><\/p>\n

By default the \u201cDisable Resolving\u201d flag is set to True (means Speed mode).  Setting it to False would cause all results to be verified with the compiler (means Accuracy mode).  Similarly the default value of \u201cHide Unconfirmed\u201d flag is True.  Setting it to False will ensure that search results will contain unconfirmed results in addition to the resolved results.  The second flag makes sense only when the first flag is set to False.  Also to be noted is that resolving\/unresolving from the results window will not affect the values of these flags.  These are global settings meant to specify default behavior.<\/font><\/p>\n

Overall, we believe that these changes have introduced more flexibility enabling users to optimize their experience based on their own needs.  We are excited about this change and hope you will like it.<\/font><\/p>\n

Thank you.<\/font><\/p>\n

 <\/font><\/p>\n","protected":false},"excerpt":{"rendered":"

Hello, my name is Raman Sharma, and I am a Program Manager on the VC++ team.  Through this blog post, I wish to highlight some changes we have made to an important feature in the C++ IDE, called \u201cFind all References\u201d.  As most of you would know, this feature is used to search for references […]<\/p>\n","protected":false},"author":289,"featured_media":35994,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[64,6],"class_list":["post-4173","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus","tag-find-all-references","tag-ide"],"acf":[],"blog_post_summary":"

Hello, my name is Raman Sharma, and I am a Program Manager on the VC++ team.  Through this blog post, I wish to highlight some changes we have made to an important feature in the C++ IDE, called \u201cFind all References\u201d.  As most of you would know, this feature is used to search for references […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/4173","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/289"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=4173"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/4173\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/35994"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=4173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=4173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=4173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}