Techno-Babble

Weirdest Visual Studio bug ever

The Bug

My loathing for Visual Studio continues.

Suddenly, every time I ever tried to search for anything, the search wouldn’t even start.  It would just say:

No Files Were Found To Look In.

Find Was Stopped In Progress

Gross.  Nothing fixed it.  Restarted.  Nothing.  

The Real Problem is that Visual Studio is Giving Me CTS

The search feature was really the one thing that made file navigation tolerable in VS.  In Eclipse, there was a “quick open” option that had an autocomplete dropdown.  Just type any part of the file name, arrow to it, and it opens the file right up.  No mousing required.  No expanding of several levels of folders and constantly scrolling within a little treeview.  It is awesome.  And it’s a no-brainer.  I can’t believe how little Visual Studio has evolved in terms of basic little usability things that make developers more productive and help prevent carpal tunnel syndrome.

But I digress.

The closest thing to keyboard-based file navigation is search.  I could just search for “class User” and I’d get a list of files that I could click into.  Not remotely as good as Eclipse, but workable.

Until this bug.

Uggh.

The Fix

Anyway, after searching around, the solution is to hit ctrl + ScrollLock, and then everything goes back to normal.  WTF?  Crazy bug.

Tags: Annoyances, Eclipse, Productivity, Visual Studio