I've used the starter kit to create a new custom module.
I ran the generated sql separately in order to create the sql server objects.
When I enter the page that contains the custom module, the list functionality works. The default record is shown to me, plus an add content and edit content link.
I'm having a few problems though.
First, the debugger doesn't seem to work with these custom modules. The breakpoints in the modules never seem to be reached. So, I reverted to old-fashioned "print statements" to debug what's going on.
If I use this.Page.Response.Write("in mycustom.ascx, at Page_Load start") I see it at the top of the listing screen, above everything else on the page, when I go to a page that has this custom module in it.
The settings page works perfectly, as far as I can tell. However, if I put a similar print statement in all its routines, the text never shows up. I even threw an exception on purpose, as the first command in the settings control's routines, but as far as I can tell, it never got thrown.
The Edit page doesn't do anything, as far as I can tell. It just blanks out that content pane and nothing else happens. If I put the same type of message or thrown exception in the edit control, nothing different happens.
I'm stumped!
First, how can I get the debugger to work in these controls? That would probably help me figure out what else is going on.
Second, any clue as to what's going on?
Thanks in advance!