09 Nisan 2012 Pazartesi 23:02
I am finding that the F3 key loops endlessly through the same open document if I move the cursor after it finds its match. If I do not move the cursor, F3 will go on to the next match in the next document. This in different than how it worked in VB6, where it would find the match in the next document if there were no more matches below the cursor in the open document. Now it goes back to the top of the open window.
This is annoying as I often want to see what comes after the thing I am looking for, and if the line is long then moving the cursor to the end of the line is the easiest way to do this.
I can reproduce this behavior. Please let me know if there is a way to restore the "find next" behavior of VB6. Thanks for your help.
10 Nisan 2012 Salı 13:59
Your question is Regrading VB6.
So Please post your question in below forum for appropriate answer.
10 Nisan 2012 Salı 16:13
No, it is not. I am talking about Visual Studio 2010 program editor. My question is how to get the find-next functionality in the Visual Studio Editor to work as it did before, and why it does not find the next match, but rather the first match in the open document.
I have no questions about VB6. I hope cleared this up for you. Thank you again for your help.
- Düzenleyen Bob Kohn 10 Nisan 2012 Salı 16:14
11 Nisan 2012 Çarşamba 06:38Moderatör
>>This in different than how it worked in VB6, where it would find the match in the next document if there were no more matches below the cursor in the open document.
You can try to set the find scope to "Entire Solution". you can select it in the Look in box in the Find and Replace dialog.
If I have misunderstood anything, please feel free to let us know.
Lucy Liu [MSFT]
MSDN Community Support | Feedback to us
11 Nisan 2012 Çarşamba 14:03
please post your question also on
13 Nisan 2012 Cuma 16:48
I already had the scope set to the "entire solution".
Again: when you use the F3 key to find the next match, it loops back to the top of the current document if you had moved the cursor after it found the last match. It says "passed end of document" in the status bar but it goes back to the top. If you simply keep hitting F3 without moving the cursor, it finds the match in the next document. This is not the way it had worked in VB6, where it would always find the next match in the next document if there were no more matches below the line in the open doucment.
Please let me know if this can be corrected. Thanks again.
16 Nisan 2012 Pazartesi 09:39Hi Bob, I can't reproduce this behaviour in VS 2010 SP1 with scope set to entire solution. Caveat: I do have the Productivity Power Tools add-in installed so I'm not necessarily comparing like with like.
16 Nisan 2012 Pazartesi 16:52Thanks for looking into it. I will see if I that add-in takes care of the problem.