Better file searching (on Windows) with a powerful, fast, easy tool
For years I've used a great freeware tool, Agent Ransack, and I (as well nearly everyone I show it to) love it for several reasons. Beyond fast, effective, and easy searching, it also has a cool regular expression building wizard that may be reason enough to use the tool when you need to create a RegEx quickly. It's the freeware version of a commercial product, File Locator Pro, and can be found at www.agentransack.com.
BTW, I do realize that the Windows File Find feature can be enhanced by using its available Indexing Service. I've never been a fan of that for various reasons, and many won't enable such (for good reason) on production servers. Yet you may need to search for files on such a server. This tool can do it with little overhead. Sadly, some people may not ever do searching for files by name or content (or suffer productivity) simply because the available tools are so poor. This one will change your mind!
Definitely favored over other search tools/editors
Since learning of it in about 2004, I no longer use the find feature within editors like Eclipse, DreamWeaver, CF Studio, or various notepad alternatives to search across multiple folders anymore. AgentRansack is so much faster than those in my experience.
It's also not only faster than Windows find, too, but unlike that (in some versions of Windows), it DOES search for content in ALL file types. Have you ever used Windows find to search text in CFM files, and found that it never finds files you know it should? The problem is that it has an internal list of file types it will search, and all others it will simply ignore. It also ignores files marked with the hidden and system attributes, which may not be expected. (By Windows Find I'm referring to the feature available from the Start menu or via WindowsKey-F).
And unlike using your editor to search, it doesn't lock up your editor while it's searching away. And even then, it's really FAST! I find it can search gigs of content in just a few moments--yet it DOES NOT rely on indexing the content in any way.
Another great benefit it has over the other more traditional search approaches is that while the left pane is showing the files it found in its search, a right pane shows (for any file you select on the left) the lines WITHIN the file that matched the search. Yes, in some other search tools the search results pane allows you to click a result to open the given file at the given location where the search result was found, but this approach in AR is just much simpler and more effective, I think.
Perhaps most powerful, it also integrates with the Windows Explorer interface, so it's easily reached by a right-click on any folder to search that folder and its children.
Bonus Regex Feature
As I hinted above, beyond searching, AR is also great for its really nifty regular expression feature, to help build regex's declaratively (with a wizard-like interface). I find myself opening it just to create a RegEx when needed. More than that, there is also a useful "test" menu option where you can enter a RegEx, and some text against which to search, and it will show what the regex would find in that text. Very handy.
Check it out
Everyone I've shown it to has been impressed. Check it out.
You can see screenshots of 3 main parts of the interface in use (including the regex wizard and results viewing aspect) at the site.
The only negative with the tool is its name. Some folks have cringed when I've proposed installing it while trying to help them solve one issue or another. But when they see it's a freeware version of a commercial tool, that generally tames their nerves. The very quick install and immediately obvious benefits quickly wins them over.
I should also mention that this is one of dozens of such file/find tools that I list in a vategory for their type at my CF411 site, listing over a thousand told and resources of interest to CFers.
Enjoy.
Someone who had learned of my
So, as explained in the article (which shows you the actual steps in IIS), I configure different IIS virtual directories called _cf5, _cf6, _cf7, and _cf8. I set each to points their CFM extension (and related CF ones) to the appropriate web server extension that would be used if I'd configured each server to work with IIS (like C:\CFusion\BIN\ISCF.DLL for 5, C:\CFusionMX\runtime\lib\wsconfig\1\jrun.dll for 6, and so on).




