I’m pleased to announce Entrian Source Search 1.4.17, which includes the following features and fixes:

• Save keystrokes: When you search for files using a file: / dir: / ext: / age: filter with no other search terms and there’s only one match, it will be opened in the editor automatically.  That’s 100% less wear and tear on your Down and Enter keys!  Thanks, Chris.
  
• Bugfix for very large files: Source files larger than 4MB are now always completely indexed.  Thanks, Kyle.
• Bogus error removal: Sometimes the Visual Studio editor will raise a “Catastrophic failure” exception when showing a hit, even though the operation has worked perfectly.  Rather than diligently passing these errors on, Source Search now ignores them.  Thanks, Steve.

As always, the release is available from the Source Search Download page as a free upgrade for licensed users and as a 30-individual-day trial for everyone else.

I’m pleased to announce Entrian Source Search 1.4.15, with these features and fixes:

• F# support:  Hello F# developers!  For those who are new to Entrian Source Search, it’s a Visual Studio addin that builds a full-text index of your source code, giving you instant, syntax-highlighted search results.  It supports fuzzy search, proximity (loose) search, autocomplete, age filtering and much more:
   

  Note for existing users: if you already have F# code in your index, you’ll need to force a refresh to get it highlighted. Thanks, Jack and Vasily.

• Performance boosts for indexing.  Overall indexing performance is up by about 25%, and by more like 50% for large files.
• New hotkey Shift+Alt+Num * performs a substring search by taking the word under the cursor and adding leading and trailing asterisks, like *this*.  Thanks, Chris.
• Corrupt file system events from network file servers no longer cause files to transiently disappear from the index.  Thanks, Jean-Michel.
• License names containing ampersands are now displayed properly in the License Key dialog.

You can download this latest release from the Download page.

Update (1.4.16): F# double-backtick identifiers ``like this`` are now respected – they are syntax-highlighted properly, and if you hit Alt+= on one of them then Source Search will search for the whole identifier.  Thanks again, Vasily.

Question for you F# guys: What else can I do to make Entrian Source Search an excellent tool for F# development?  I have very little experience with F#, so I’m relying on you to give me ideas.  🙂

I’m pleased to announce Entrian Source Search 1.4.14, which fixes a memory leak that could (eventually) cause an OutOfMemoryException.

The upgrade is free to existing users and available as a free trial for everyone else.  Download it here.

I’m delighted to announce Entrian Source Search 1.4.13, with two new features:

• Automatic phrase search.  You’re no longer required to use double quotes to search for phrases – by checking the new “Phrase Search” option on the toolbar, a search for One Two (without quotes) will search for the phrase One Two rather than searching for all the Ones and all the Twos:
  
  Thanks, Ondřej, Metodi, Matthew and others.
• Control over the default Looseness of a Loose search.  Previously, checking the Loose Phrases button would search for matches within ten tokens of each other – you can now control that via More / Options. (And you can still control it per-search using a query like loose50:”One Two”.)  Thanks, Ondřej.

Automatic phrase search is now the default for new installations, but upgrading an existing installation won’t enable it.

You can download this latest release from the Download page.

I’ve just released Entrian Source Search 1.4.12, which includes support for Visual Studio 2013.  It also fixes these bugs:

• Hitting the Del key to delete a result from a filter-only search (eg. ext:cpp) no longer crashes.  Thanks, Robert.
• Fixed a crash on PCs with a broken icon associated with a file type that appears in the search results.  Thanks, Yanick.

As always, the upgrade is free to existing users and available as a free trial for everyone else.  Get it from the download page.

(A Visual Studio 2013 update for Entrian Attach will be available in the next day or two.)

I’m happy to announce Entrian Source Search 1.4.11, and the fact that Source Search is now published in the Visual Studio Gallery.  If any of the Entrian faithful feel the need to enter a glowing review, I won’t stand in your way. 🙂

You can find the Source Search page here. (And while you’re there, don’t forget to check out Entrian Attach, our shiny new product!)

Source Search 1.4.11 also brings a cool new feature and a couple of bugfixes:

• You can now delete results from the results list using the Delete key (thanks for the suggestion, Steve!) If some of the results aren’t relevant, just delete them – they only disappear from the results list, without affecting your filters or your index. In the results list:
  • Delete removes the highlighted result from the list.
  • Ctrl+Delete removes all the results from the highlighted results’s file.
  • Shift+Ctrl+Delete removes all the results from the highlighted results’s folder.
• Fixed a crash when a wildcard search with multiple tokens, eg. render*( finds no matches. Thanks, Luke and Marc.
• Fixed a bogus error message when you try to show a result but you’ve modified the source code such that the result is now off the end of the file. Thanks, Alexandre.

I’m excited to announce Entrian’s new product: Entrian Attach!

Entrian Attach automatically attaches the Visual Studio debugger  to processes the moment they start, however they’re started.

Use it to debug services, web servers, code in DllMain, unit tests, setup custom actions, whatever you like.  It works for both native and managed code.

The debugger attaches as the process is created, not on a polling timer, so you get control right from the very first instruction.

You can use it to debug into child processes as well, and control whether to attach only to immediate children or to grandchild processes.

Entrian Attach knows about web servers, and you can configure it to attach to IIS or IIS Express only for certain web sites or application pools.

It supports conditional attachment for any process, according to the process’s user and/or command line.

And finally it has an “Attach Now” command to attach directly to interesting running processes, to save you digging around in Visual Studio’s Attach to Process dialog.

And finally finally, it comes with a built-in five-minute tutorial to walk you through all the features.

Download it today and give it a spin!  The Beta is free but time-limited.  The final version will cost $29 per developer.

I’m pleased to announce Entrian Source Search 1.4.10, including these features and fixes:

• You can now filter on the age of files, for instance to pick up only files modified within the past two hours: age:2h. The units are m for minutes, h for hours, and d for days. You can combine the units to say things like age:3d12h.  Thanks, Pros and others.
• New command Shift+Alt+F opens the Search box with a file: filter in place, ready to use autocomplete or wildcards to find files by name. That’s a really quick way to open any file in your source tree.
• Added Vim-familiar keys for navigating history (Ctrl+H, Ctrl+L) and autocomplete (Ctrl+J and Ctrl+K) from within the Search box.  Thanks, Reva.
• Trying to query for words that are within five billion tokens of each other via the query loose5000000000:”some words” no longer crashes (but kudos for trying, the anonymous user whose crash report revealed that bug!)
• Fixed a recently-introduced bug whereby saving a file could cause Source Search to scan all the files in that directory, rather than just re-indexing that one file.
• Fixed a conflict with Red Gate’s “.NET Demon” which could make Visual Studio hang on loading a solution.  Thanks, James.
• Pathnames between 255 and 260 characters long no longer cause a crash.  Thanks, Alex.
• The ‘Indexing’ label now only says ‘Indexing’ when it’s actually found something new or changed to   index.  When it’s just scanning for changes, it says ‘Scanning’.  Thanks, Dan.
• Added a ‘Report a bug / Suggest a feature’ command to the ‘More…’ menu.

Existing users should note that upgrading to 1.4.10 will rescan all your files, in order to pick up the modification times for age filtering.  Until that process is complete, an age filter will return partial results with a warning.  Everything else will work as normal.

• Fuzzy search: you can check the new ‘Fuzzy’ button to match:
  – variations: Archive matches CArchive and Archival
  – international spellings: Color matches Colour
  – spelling mistakes: Definitely matches Definately
  (For a large solution, fuzzy searches do go a bit slower than normal searches – they take a couple of seconds rather than being mostly instant.)
• You can now specify a filter with no search term, eg. file:*terrain* dir:renderer, to get a list of the matching files. Thanks, Reva.
• There’s now a persistent toggle for ‘loose’ phrases on the toolbar, to save you typing loose: all the time. Thanks, Rory.
• You can now use the keyboard to toggle the options from the search box: Alt+C for Case sensitivity, Alt+L for Loose phrases, and Alt+F for Fuzzy search. Thanks, Rory.
• Your selections for Case sensitivity, Loose phrases, and Fuzzy search are now remembered between sessions.
• Since phrases can now include wildcards, hitting Alt+= with char* selected now escapes the asterisk: char\*. Thanks, Ryan.
• The shortcut keys for moving through your search history (Ctrl+[ and Ctrl+] in the Search box) no longer conflict with Resharper.
• The ‘Hint’ dropdown and the tooltip for the Search box now include examples for Loose phrases. Thanks, Darker.

As usual there’s a 30-individual-day trial for new users, and the upgrade is free for existing users.

You can download 1.4.9 from the Download page.

• New feature: Loose search, which searches for matches near to each other rather than for exact phrases:
  
  The default behaviour for loose:”some phrase” is to allow up to ten tokens between the matches, but you can tune that: loose100:”some phrase” allows 100 tokens between the matches.  The terms don’t have to appear on the same line for matches to be found, nor do they need to appear in the order you give them.  Thanks, Rory and Darker.
• You can now use wildcards in quoted phrases:
  
  And of course you can combine these two features to do a loose search for wildcards.
• Breaking change: To escape an asterisk, eg. to search for char*, putting it in quotes no longer works (because wildcards now work in quoted phrases).  You need to escape it with a backslash: char\* or quote it and add a space: “char *” (which will still find char*).
• The “Partial results” warning, which has always appeared during the initial build of an index, now also appears when you add a new root directory.  Thanks, Jason.
• Fixed a very rare (like, once ever) shutdown crash (AccessViolationException).
• Adding a root directory for which you don’t have read permission no longer crashes.  Thanks, Jean-François.
• The “Licensed to” text no longer overlaps the “Hit” label when your window is very narrow.
• Source Search now works on PCs with FIPS Compliance enabled.