Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

advice on web page layout

Status
Not open for further replies.

ASPnetNovice

Programmer
Apr 28, 2005
19
US
Hello,
I am making an ASP.NET site. I have created several .aspx pages and some have web user controls(.ascx) that I made on them.
I now wish to use the content on these pages on a 'master page'. I originally wanted to use frame sets but when investigating inter-operability with ASP.NET I found out that entire web pages(.aspx) can be converted into web user controls. One can then place these controls( with page content) on another page that acts like a master. Alternatively one can, I understand, use div/layers to achieve a similar functionality. What do you guys think about the best approach. What I was hoping to avoid was a replication of redundant content on each page (menus, logos, etc...) Take a look at this site - this entity (ProjectComplete.com) claims that it provides a content mastering system called Web Form Maestro. I intuitively understand their approach (using xml) but was hoping for input from people who know more than me before going too deep along any one road.
 
Dreamweaver templates and Visual Studio are pretty much the standard.
There is no need to use XML where it is not needed. It can make a simple system complicated and hard to manage. XML is not intended to be edited freely with a text editor, it is very easy to break and very hard to track down the source of the problem.

If you don't have Dreamweaver then just use ASCX files for your header footer and nav system. Redundant html code is not hard to manage when it is done right. Full dynamic (homemade) systems generally have to junked when it comes time for someone other than yourself to work on it.
Search engines prefer real files names too, rather than (basepage.aspx?page=aboutus) one page dynamicly loading static content.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top