By Jerome at June 19, 2007 07:08
Filed Under: .NET
There are bugs, mystical bugs I may add, that no one has been able to reproduce, nor find a fix for, well at least that do work on every occurrence. VS2005 has one of these, where when you try to use "find in files", you get a "No files were found to look in. Find was stopped in progress." and that's it. No disk access, no registry relevant access, no relevant file access.
Some have found that pressing Ctrl+Scroll Lock may help, well, it did not help for me. Some other tried the reboot, which seems to work better. You can also spin around three times on your chair before doing that, that might also help.
Then I remembered that some times, because it seems that the CLR maintains some kind of "cross process state" (I don't know what it acutally is, so I'm just guessing) that cripples all the .NET processes that are running. The only way to reset that state is to kill all processes that are using the CLR.
That means killing every standard application, plus IIS's aspnet_wp, and if you have .NET 3.0, PresentationFontCache.exe, ...
That did the trick for me, after killing all these processes and running VS2005, my search was up and running :)
8aa6df4a-545b-4fa0-b7c3-26497a461a7c|1|4.0