Many times adding the implementation of ISearchable to an already registered and working module does not result in the supported features in the module's registration (Host --> Extensions) being updated. I would begin by checking the module's registration to verify that Searchable is checked in the supported features list. If it is not, try clicking "Update" then re-open/edit the module's registration to see if it is now checked.

Also, make sure that the module's registration includes a reference to the module's Business Controller Class in which you implemented ISearchable. Without that information the search indexing scheduled task will not be aware that your module supports ISearchable.

Finally, if you do need to debug your implementation of ISearchable you should be able to open your module project in Visual Studio, etc., compile it in debug mode, then set a breakpoint at the top of the implementation of the GetSearchItems method. Open your localhost site in your favorite browser then in VS attach to the site's ASP.Net worker process (w3wp.exe). When logged into the site as host user navigate to Host --> Schedule and edit the "Search Engine Scheduler". Make sure that the scheduled task is enabled and click "Run Now". This should force all modules which implement ISearchable to re-index their content during which the breakpoint you set should be hit.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I eventually figured out what was wrong.  I was correct insofar as the indexer was not running.  If I entered the controller class via DNN it didn't work.  As soon as I added the controller class to the DNN manifest, the indexer started working.

I also got the debugger to answer a few times but it seems dicey.  I can't always find the DNN worker thread in the list of processes I'm allowed to attach.