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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Exploring Node.js Internals

I found a great article explaining Node JS internals, must read : https://www.smashingmagazine.com/2020/04/nodejs-internals/ Some other articles : Introduction to Node.js Being an official website, Node.dev explains what Node.js is, as well as its package managers, and lists web frameworks built on top of it. “ JavaScript & Node.js ”,  The Node Beginner Book This book by  Manuel Kiessling  does a fantastic job of explaining Node.js, after warning that JavaScript in the browser is not the same as the one in Node.js, even though both are written in the same language. Beginning Node.js This beginner book goes beyond an explanation of the runtime. It teaches about packages and streams and creating a web server with the Express framework. LibUV This is the official documentation of the supporting C++ code of the Node.js runtime. V8 This is the official documentation of the JavaScript engine that makes it possible to write Node.js with JavaScript.
Post a Comment
Read more

Hibernate Object Conversations

Session methods to use for object conversations Save() A new instance being attached to the session. An insert will be scheduled. Update() Call Update to make a transient object persistent again. It will force a SQL update on the transient object. This is because Hibernate does not know whether the object is dirty or not and to be safe by default schedules an update. This method will throw an exception, if the entity is already registered with the session. - NonUniqueObjectException is thrown. saveOrUpdate() Either a save or an update will be called based on whether the identifier exists or not. No identifier - save is called, else update is called. Or for a better understanding, if the object is transient, then a save is called, if the object is persistent, then an update is called. Reattaching an unmodified instance - If you know for sure that an object is not modified and you just want to make it persistent again - Session.lock(item, LockMode.No
Post a Comment
Read more