Entrian Solutions
 

Entrian Source Search 1.4.15: F# highlighting, speedups, hotkey for substring search

Sunday, November 10th, 2013 by

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

 

2 Responses to “Entrian Source Search 1.4.15: F# highlighting, speedups, hotkey for substring search”

  1. Tobias Says:

    Two features are missing for productive work:

    - Limit the results to certain project(s) in the solution
    - Include XAML to the search index

  2. Richie Hindle Says:

    Hi Tobias,

    Thanks for the feedback!

    You can limit your search to certain subdirectories using a dir:dirname filter, which is not quite the same as filtering per-project, but personally I find it’s more often what I want.

    XAML files should certainly appear in your index – is it possible you’ve set up an exclusion pattern that’s causing them not to be indexed? Or that your index root needs to be higher up your source tree?

Leave a Reply