Entrian Solutions

Archive for August, 2009

Entrian Source Search 1.3.3: Custom sort, custom verbosity, and more

Monday, August 31st, 2009 by Richie Hindle

Entrian Source Search 1.3.3 brings you a whole slew of enhancements:

  • You can now sort the results by folder name, by filename or by file extension (thanks, Rob and Pros):
    Column sorting
  • You also get incremental search within the results, so you can focus the results and then type the first few letters of a filename or folder name to jump directly to it.
  • You can now control how much text appears around the actual hit in the “Hit” column, via the new “Verbosity” slider:
    Verbosity slider
  • The toolbar button labels are hidden when there isn’t enough space for them, so the buttons don’t disappear into the toolbar overflow:
    Hidden toolbar labels
  • When the Hit column gets narrow, the context shrinks so you can still see the hit text properly.
  • When the Folder column gets too narrow for the folder pathnames, the pathnames are now truncated from the left rather than the right, leaving the most important pieces visible.
  • The tooltip for truncated items in the results list no longer times out (thanks, Grammarian).
  • Added a workaround for a bug in early versions of .NET 2.0, which could cause an ArgumentOutOfRangeException when searching (thanks, Eldad).

As always, the upgrade is free for licensed users, and there’s a free 30-day trial for everybody else.  Download here!

Entrian Source Search 1.3.2: Out Of Memory errors and window positioning

Wednesday, August 19th, 2009 by Richie Hindle

This release sees two enhancements:

  • The window position is once again remembered properly between sessions.  (This was partially broken in 1.3.0, because of changes needed for Visual Studio 2010, but should now work properly on all versions.)
  • If a search returns so many hits that it runs out of memory, you now get a sensible error message rather than a crash:
    The "Out of memory" message

If you’re getting Out Of Memory errors when searching, you might be using the wrong search syntax.  Searching for this:

  x = 1

(with spaces around the equals sign) will actually search for all the x‘s, all the = signs, and all the 1‘s in your code!  You need to either use a quoted phrase:

  "x = 1"

or simply omit the spaces:


Spaces are ignored when searching, so searching for x=1 (without spaces) will find x = 1 (with spaces).

As usual, you can download this latest release from the download page.