I’m very pleased to announce Entrian Source Search 1.3.14, which fixes the following issues:

• Using your text editor font for the search results no longer suffers a resource leak (thanks, Mark)
• Index optimization now never happens when you’re using your PC, but instead waits until there’s been no mouse or keyboard activity for at least five minutes (thanks, Anton)
• The Verbosity slider is now effectively unlimited, allowing your search results to take up the full width of the screen (thanks, Stoney and Pierre-Olivier)
• In Visual Studio 2010, hitting the Alt+= hotkey now puts the focus into the search box even if the Entrian Source Search window wasn’t previously visible (thanks, Christian).

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

You can download this latest release from the Download page.

If you’ve ever tried (as I was trying this week) to debug a loader problem on Windows, you probably know about the very useful gflags application.  It’s part of the Debugging Tools for Windows, and one of the things it does is enables “loader snaps” for a process.  That tells the Windows loader to send a whole bunch of useful information to the debugger console as it loads an executable and its DLLs.

Except that it doesn’t.  Not if you’re running on 64 bit Windows, developing a 32 bit application.  If you just follow the obvious download links for the Debugging Tools you’ll get the 64 bit version, which will quietly ignore your request for loader snaps for your 32-bit application.  To set the appropriate flags you’ll need to install the 32-bit Debugging Tools and use that version of gflags.

I’m happy to announce Entrian Source Search 1.3.13, which fixes an error when opening XAML files for Windows Phone 7 (thanks, Anton!)

You can download Entrian Source Search 1.3.13 from the usual Download page.

Hot on the heels of 1.3.11 comes Entrian Source Search 1.3.12, which fixes two bugs:

• The hit count and search time (“120 hits in 23 files, 0.11 seconds”) would sometimes fail to update after you hit Search.
• There was a resource leak that would (after many days of use!) cause Visual Studio to run out of GDI resources and start to suffer painting glitches.

Download Entrian Source Search 1.3.12 from the Download page.

I’m happy to announce Entrian Source Search 1.3.11, which brings you the following features:

• You can use your text editor font for the search results, rather than being stuck with Microsoft Sans Serif (thanks, Mark)
• You can force a refresh of all files in the index (rather than just the changed files)
• You can choose how to interpret 8-bit source files that have no UTF-8 BOM (thanks, Alexei).

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

You can download Entrian Source Search 1.3.11 from the Download page.

I’m happy to announce the release of Entrian Source Search 1.3.10, which fixes three bugs:

• Very occasionally, Source Search could throw an ArgumentOutOfRangeException when you hit Search.  Now fixed.
• When you try to view a search hit in a non-existent file (for instance because you’ve deleted a huge pile of files and the index hasn’t caught up yet), the error is reported properly, rather than giving a cryptic “Value does not fall within the expected range” message (thanks, Joe).
• When showing a search hit in a .sql file, Visual Studio no longer occasionally shows an error message when there was no error (thanks, Stoney).

You can download 1.3.10 from the usual place.

Entrian Source Search 1.3.9 introduces a “Force index refresh” command.  This isn’t necessary for most people because Source Search automatically re-indexes changed files as soon as they hit the disk, but some users whose source files are held on network drives have found that changes aren’t always picked up.  (Thanks, Christian.)

Exclusion patterns are now case insensitive (thanks, Ike).

You can download 1.3.9 from the usual place.

If you’re having trouble with iPlayer on a mobile device over WiFi, this may be of some help:

I recently installed a Netgear DG834 ADSL 2+ modem router.  It works beautifully.

My other new toy is a T-Mobile Pulse Android phone.  A lovely bit of kit for not very much money.

Trying the excellent beebPlayer application (an iPlayer client for Android) I found that quality was far worse on WiFi than on 3G.  Surely that can’t be right?

To cut a long story short, the DG834 has a feature called Port Scan and DOS Protection, which as it turns out interprets the incoming RTSP packets as a DOS attack and drops most of them.  Switching the feature off (under Advanced / WAN Setup) makes it all work perfectly.