There are two normal reasons for #INCLUDE in ASP.
1. Code used in various pages
2. UI elements
For pure code, stick it in its own class and call that class. For pure
helper methods, make them static (Shared in VB.NET).
For UI elements and/or UI and code, create a control. The easiest to get up
and running quickly is a web user control, or .ascx file.
In 2.0, you can also put common information into master pages to easily
"chrome" your site (menus, et al).
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"David" <db****@simnet.is> wrote in message
news:un**************@TK2MSFTNGP12.phx.gbl...
As very often is the case a web page has a main, dynamic content page and
a surrounding, more constant "frame" (not html frame!) for stuff like menu,
logo, links etc. In my old ASP web pages I solved this by using #include
so that each .asp page simply started with including this in the top of the
file. Actually it was also ASP code since some of the frame content was
dynamically created from the database.
I can see many possibilities now with .Net to do this but which one would
you suggest?