After reading the Michael Washington tutorial, and following it closely, I am not able to get my module to recognize ISearchable interface in  my controller class.

This is my controller class

Namespace MNO.Modules.KNB
<DataObject(True)> _
Public Class KNBController
Implements Entities.Modules.ISearchable

 Public Function GetSearchItems(ByVal ModInfo As Entities.Modules.ModuleInfo) _
As DotNetNuke.Services.Search.SearchItemInfoCollection Implements Entities.Modules.ISearchable.GetSearchItems
' Get the Surveys for this Module instance
Dim Topics As List(Of TopicsInfo) = ListKNB_TOPICS(ModInfo.ModuleID)
Dim SearchItemCollection As New SearchItemInfoCollection
Dim TopicsInfo As TopicsInfo
For Each TopicsInfo In Topics
Dim SearchItem As SearchItemInfo
With CType(TopicsInfo, TopicsInfo)
Dim strContent As String = System.Web.HttpUtility.HtmlDecode(.Title & " " & .Summary & " " & .Keywords & " " & .Details)
Dim strDescription As String = HtmlUtils.Shorten(HtmlUtils.Clean(System.Web.HttpUtility.HtmlDecode(.Summary), False), 100, "...")
SearchItem = New SearchItemInfo(ModInfo.ModuleTitle & " - " & .Title, _
strDescription, _
.CreatedByUser, _
.CreatedDate, _
ModInfo.ModuleID, _
.TopicId.ToString, _
strContent, "TopicId=" & .TopicId.ToString)
SearchItemCollection.Add(SearchItem)
End With
Next

Return SearchItemCollection

End Function

In my Module definition I have this in my Controller class field: MNO.Modules.KNB.KNBController

When I hit update, ISearchable does not get checked. This module controller class is in the app code folder, does that make a difference?

Help! This portal runs 4.5.1

Thanks for the reply, I've been out on holiday the past few days. I did hook that controller method up to a datagrid and I do get results. Regardless, even if there were no results (as there wouldn't be with a new module install) shouldn't the ISearchable box be checked in the mod definition?

I'm not sure how to troubleshoot this, since I can't get the breakpoint to trip in debugging.

Thanks.

I recall submitting to Gemeni an issue with the optional interfaces not being recognized after clicking Update back in version 4.5.0 but can't recall if it was fixed in version 4.5.1 or if the fix did not occur until 4.5.3. Is it possible to access the change logs for specific earlier versions?

When you mention that the module controller class is in the App_Code folder, is it in the root of the App_Code folder or in a sub-folder that has exactly the same name as the sub-folder under DesktopModules in which the module itself resides?  I've previously run into a few problems with the module definitions (specifically not recognizing supported features and not being able to create a module package) when there has been a mismatch of folder names.

---

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