Skip to main content

No files were found to look in. Find was stopped in progress

This error is a bug in Microsoft Visual Studio which occurs very often when “Find in files” utility is used to find some token in a file or directory which has been specified in the Look in list of the Find in files dialog box.

Visual Studio will just dump this message: “No files were found to look in. Find was stopped”, and will not even try searching in the files.

To correct this error :

1. Either, Get your Visual Studio in focus and press any of the key combination :
  1. CTRL + BREAK
  2. CTRL + SCROLL LOCK
  3. ALT + BREAK
Note : Not sure what does this key combination does but it works.

2. Or, Delete this Registry key from Windows Registry using Regedit utility :
MyComputer\HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Find
and restart your Visual Studio.

Comments

Popular posts from this blog

JUnit – Run unit test in an Sequence / Order

In JUnit, we can use @FixMethodOrder(MethodSorters.xxx) to run the test methods in a sequence or order.

import org.junit.FixMethodOrder;import org.junit.Test;import org.junit.runners.MethodSorters;importstatic org.hamcrest.CoreMatchers.is;importstatic org.junit.Assert.assertThat;//Sorts by method name@FixMethodOrder(MethodSorters.NAME_ASCENDING)publicclassExecutionOrderTest{@TestpublicvoidtestB(){assertThat(1+1,is(2));}@Testpublicvoidtest1(){assertThat(1+1,is(2));}@TestpublicvoidtestA

Create Runnable Jar - Eclipse Options

When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JARPackage required libraries into JARCopy required libraries into sub folder next to JAR. What are differences : Extract required libraries into JAR - Extracts the actual .class files from the libraries your app uses and puts those .class files inside the runnable JAR. So, the runnable JAR will not only contain the .class files of your application, but also the .class files of all the libraries your application uses. Package required libraries into JAR - Puts the actual JAR files of the libraries into your runnable JAR. Normally, a JAR file within a JAR file cannot be loaded by the JVM. But Eclipse adds special classes to the runnable JAR to make this possible. Copy required libraries into sub folder next to JAR - Keeps the library JARs completely separate from the runnable JAR, so the runnable JAR will only contain the .class files of your application. Option #2 is convenient be…