This is what a search and replace does. It's how it works. How do you expect for the search to find something if it doesn't go thru everything?? That's the whole point. Do you know where the keywords are already? Can you navigate to them?

I have not found that search and replace is slow in Visual Studio (I assume that is what you are asking about, you have not specified). Perhaps your code files are getting too big and you could break apart functionality to keep the individual files smaller.

Is it possible that you have the search settings set to search all files or all open documents instead of just the current document? Searching thru other files would be noticeably slower.

-Peter