AyriA (ayria) wrote,

  • Mood:
  • Music:

VS2005 ... Rage.

If you're ever feeling angry because Visual Studio managed to suddenly mess up for no apparent reason again -- maybe the find functionality just suddenly stopped working? Maybe you got a message similar to the following?

Find all "MySearchString", Subfolders, Find Results 1, "Entire Solution", "*.*"
No files were found to look in.
Find was stopped in progress.

Although I had been using the Find in Files functionality earlier in the day, it seemed to stop working when I decided to use it this afternoon. The quiet rage that had been slowly building up would probably have exploded in all kinds of nasty ways. In any case, to curb this oncoming fit of rage, simply press the following key combination to solve your undeniably random Visual Studio problem.


Yep, the solution is that simple. And yet the problem still doesn't make any more sense than the solution to the problem. Pressing Scroll Lock in combination with Ctrl or by itself does not actually cause the problem to be reproduceable after being fixed. So what gives?

Perhaps you've had other problems in Visual Studio where the embedding manifest stage just never finishes. I know I have. I'm not sure yet why this happens, but it does seem to occur from time to time. I'm sure there's an explanation, though I hesitate to say that it would be "perfectly rational". If anyone has figured out which temporary files I should be deleting to resolve this problem, I'd really love to know. All I know is that it has to be something temporary since everything is all dandy once I reboot the computer. Oh Visual Studio, so useful, and yet so painful to use.
  • Post a new comment


    default userpic

    Your IP address will be recorded