What you are doing should be referenced by each page. When you click a button in your header, which is located on your master page, you want the main content to change? This is done by just going to the next page, that references the master. This is still a server call, so it's exactly as going to the next page.
So, with your master page created, now create your content pages that just reference the contentplaceholder from the master, which is the control asp:Content.
It is it's own separate page, so you just go from page to page, where your master will stay the same. You do this by setting your master in the head line of the document. It will do the rest itself.
However, with your header as a contentplaceholder, if you have buttons in them, you will have to either copy the code to each page you use with that header, or just make the header part of the master page.
Does this make sense?
The master page will be standard among all pages that reference it, or among all pages if hard-coded into the web.config file.
Then each page that has the content just references the master page and only place the content in the appropriate content holders. Any code not within those holders will throw an error.
SheSaidImaPregy
Veteran Poster
1,080 posts since Sep 2007
Reputation Points: 43
Solved Threads: 68