Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 2.0 > ASP.NET 2.0 Basics
|
ASP.NET 2.0 Basics If you are new to ASP or ASP.NET programming with version 2.0, this is the forum to begin asking questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Basics section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old February 1st, 2006, 04:59 PM
Authorized User
 
Join Date: Jan 2006
Posts: 91
Thanks: 0
Thanked 0 Times in 0 Posts
Default Master Page ContentHolders - bulky in designer

(alert: newbie-crossing ahead)

When working in designer with a page that uses a master page, I can't seem to minimize the contentholders from the master page past a certain extent. So they overlap, and they are sort of "in the way" of each other, visually and in terms of clicking on other parts, when I'm working on the page.

Is there any mitigation for this? Or am I making incorrect assumptions here about filling these content areas?

I thought at first that the master page would be a "sub-page holder"...but then I realized that it's just a template. So now I'm thinking you have to make a "working" page that uses the master page, and then put the "sub-pages" in the content areas of the working page. And the sub-pages are going to be...not really pages, but chunks of content, so maybe...user controls?

(I've got three books on this, but, unfortunately, I'm documentation-and helpfile-lexic...I only seem to be able to learn (at least at first) from code examples and trial and error, until I get the functional flow of the thing.)

Any guidance on this would be appreciated. (The master page behavior...not my learning proclivities... :)
Thanks!
 
Old May 30th, 2006, 01:02 PM
Friend of Wrox
 
Join Date: Apr 2005
Posts: 190
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Wirerider:

The master page is not just a template. Rather, it is the part of every page that inherits from it. When you put objects in the place holder(s) your are adding to what is already there.

I have had position problems with controls I place in the placeholder. I solved them by
setting the VWD tool option to not generate any style data by default for every control.
Later, when I get all the objects on an aspx page that I want, I then go create either a
style parameter for every contol by hand, or make a style sheet for every page, which amounts to the same thing.

As far as learning how to do new things, I can't imagine how learning to do things via trial and error could possibly work given the number of classes, properties, methods that
exist in the .net world.

VV







Similar Threads
Thread Thread Starter Forum Replies Last Post
Master Page Method: Code-Behind for Content Page kwilliams ASP.NET 2.0 Professional 3 June 2nd, 2008 12:57 PM
Master Page and Content Page with Java script Harjinder ASP.NET 2.0 Professional 1 February 1st, 2008 10:31 AM
Access Master page control from Content page. angshujit ASP.NET 2.0 Basics 3 January 11th, 2007 06:20 AM
content page viewstate value in Master Page cbe_seenu ASP.NET 2.0 Professional 0 August 1st, 2006 01:01 AM
Embedding Report Designer in ASPX Page gagansharma Crystal Reports 0 February 16th, 2004 07:53 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.