Okay, I guess I need some help here.  I have created several modules, and most of them implement the iSearchable interface.  I am now working on a new module and the iSearchable is not working.  So, in the process of trying to figure out why it was not working, I came across this error message in the admin events log:

Could not load file or assembly 'Comsite.Modules.Classifieds' or one of its dependencies. The system cannot find the file specified.

Every time I "restart Application" from the Host Settings screen it adds another of these errors to the log.  So, I assume it has to do with the iSearchable beginning to process all the modules that are searchable.

Okay, here is the odd thing... When I noticed Comsite.Modules instead of ComSite.Modules (notice the S is capital) I realized that I may have not always typed it the same in the namespace declarations.  So, I performed a global search and replace on Comsite. with ComSite.

Okay, so in code I now know that the casing is correct.  So I went into the DesktopModules table and updated all the references to the lowercase version to match the correct case version.  The odd part is that now when I "restart Application", the error that results is still using the lowercase version!!!

so it's trying to find Comsite.Modules.Classifieds instead of ComSite.Modules.Classifieds.  Does anyone have any idea what I may be missing?

Thanks in advance!

I'm not sure about the case sensitivity, but would also check the Attributes column of the EventQue table particularly if you also implemented IUpgradable in this module? Look for a row in which IsCompleted is false (0).

ON EDIT: Brian, you beat me to that one as I was writing the post!!

---

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

Have you double checked that your module definition has the right features marked?  If you marked the row as completed, it may have never evaluated the correct business controller class to verify which features your module implements.  I believe that hitting the Update button on the module definition page should cause it to re-evaluate that class.

Hope that helps,

---

Brian Dukes Engage Software St. Louis, MO 866-907-4002

DNN partner specializing in custom, enterprise DNN development.