Well, I got through the last obstacle with the references, but now I am faced with something else.  I am aware that the dreaded "MinMax persistance type of cookie requires a ModuleId" problem is most likely related to a namespace issue.  That makes sense in my case, because I know that in all the new coding I've done I have probably hosed something.

I've tried looking a the log viewer and it doesn't seem to be much help, namely because I can't figure out where to put a break point in my code to find the root of the problem.  I can see that the visibility control is being passed an invalid moduleid (-1), so my module isn't being loaded properly, but I can't figure out where exactly this is happening.  I have tried putting a break point in default.aspx.vb and following the process from the creation of the page, but I can't seem to see where the assembly load is failing.

Any ideas on how to trap this?  I've always found that debugging a problem is 90% finding it, and this seems to be a solid case in point!

Any help is appreciated...

Davey Bolling