G
Guest
Hi, basic question here - I'm struggling with the transfer from asp to
asp.net a bit, especially in seeing the 'bigger picture' of how things are
best structured.
I have a website made up primarily of aspx pages. I have separated out the
common <head> as an .ascx file and intend to do the same for other common
regions of html.
In the aspx.vb I have code that is common to all pages. For example a sub
which is passed a parameter to tell it the url of the page and builds a menu
with the current page highlighted, and another which passes in Page Title to
the .ascx mentioned above.
Being common code (just the param that varies), I would like to extract
these routines and effectively have one aspx.vb which is common to all aspx
files. How do I do that? All aspx sharing a single codebehind, or at least
inheriting from the common one, and being able to override code in their own
code behind.
Are there any really good books/online tutorials that cover this sort of
architecture planning?
Cheers,
Richard
asp.net a bit, especially in seeing the 'bigger picture' of how things are
best structured.
I have a website made up primarily of aspx pages. I have separated out the
common <head> as an .ascx file and intend to do the same for other common
regions of html.
In the aspx.vb I have code that is common to all pages. For example a sub
which is passed a parameter to tell it the url of the page and builds a menu
with the current page highlighted, and another which passes in Page Title to
the .ascx mentioned above.
Being common code (just the param that varies), I would like to extract
these routines and effectively have one aspx.vb which is common to all aspx
files. How do I do that? All aspx sharing a single codebehind, or at least
inheriting from the common one, and being able to override code in their own
code behind.
Are there any really good books/online tutorials that cover this sort of
architecture planning?
Cheers,
Richard