Hi again...

Erm... i'm going to go about doing my site/application in little modules.... namely ASCX Files.

Now to start with I had one big page defining the structure of the site in tables... any nested tables i've passed into ASCX files and called them in to the higher up page through the @Register. So I do have nested ASCX pages.

Now am I right in thinking that I could write code to interact with these different modules without making any other 'pages', but create ASCX files that plug and play, and have .vb files behind each ASCX file to provide event handling to change the ASCX file loaded into each? etc etc

My site is quite basically laid out int he following order header, upper navigation, content (the sections across... called tripages: introduction, interaction, intervention), hints section (small line with gobal messages/hints etc), then below that lower navigation bar, then footer.

Now will I get problems passing objects variables/events from one ASCX to another if they are nested?

Good or not?

Thanks,
Deian

I've never found any code that was plug and play! ;)

To get control to control interaction it's best to use events. You can wire together events in the container (ASPX or ASCX). You can't really write code in one control that talks to another control, because the controls are instanciated in the container and one control wouldn't be able to get a reference to the other control(s). The container would have to provide a reference or you would use events. IMHO the best form is to use events. That way you won't have any worries about controls failing to "contact" other controls.

You won't have any problems with events between nested controls.

If you are looking for a "templating" solution you might want to have a glance at this: http://www.geekdork.com/SkeletonCore.

Peter
------------------------------------------------------
Work smarter, not harder.