> useful info, having said that I've found usercontrols more hassle than
> they're worth. IMHO its better to use webcontrols if possible - they're
more
> work to code but a lot more flexible + you can see them at design time. I
> build whole common page sections into webcontrols making the aspx pages
very
> small.
>
> Also, rather than have my pages inherit from System.Web.UI.Page, I have an
> intermediary 'BasePage' class and inherit my pages from that. Experiments
> with inheriting actual aspx pages really screwed the designer as any
> designer components in the base page get added AGAIN into the inherited
page
> :o( If you add controls dynamically (which again is less hassle) then its
> fine and saves a lot of duplicate coding!
>
> As for actual page layouts, cascading style sheets (CSS) are the way to
go.
>
> HTH
>
> Simon
>
>
> "Brian W" <brianw@gold_death_2_spam_rush.com> wrote in message
> news:OZoGRPSBEHA.3568@tk2msftngp13.phx.gbl...
> > "Joerg Jooss" <joerg.jooss@gmx.net> wrote in message
> > news:%23Xza0t4AEHA.2480@TK2MSFTNGP11.phx.gbl...
> > > Brian W wrote:
> > > > Check out one of Paul Wilson's article on Page Templates.
> > > >
http://www.wilsondotnet.com/Default.aspx > > >
> > > There are actually quite a few Page Template "patterns" published for
> > > ASP.NET. Check out site like
www.asp.net or
www.apsalliance.com for
more
> > > information on this topic.
> >
> > Could you be a little more specific, please? Even at those places the
only
> > references I found where to Paul Wilson's work.
> >
> > Thanks
> > Brian W
> >
> >
> >
>
>