ASP.NET MVC nested master pages, inherit content

Question

I have a series of nested master pages, like so:

site.master:

<asp:ContentPlaceHolder ID="SearchFormContent" runat="server">
<%Html.RenderPartial("SearchFormControl"); %>
</asp:ContentPlaceHolder>

in the nested (child) master page, area.master

<asp:Content ContentPlaceHolderID="SearchFormContent" ID="SearchFormContentContainer" runat="server">
<asp:ContentPlaceHolderID="SearchFormContent" runat="server"/>
</asp:ContentPlaceHolder>

I have two separate content pages. One wants to add its own content to SearchFormContent, the other would like to keep the content that was defined in the top-level master page. Of course, since the child master page defines content for the SearchFormContent block so that the child pages can potentially access it, the content defined in the top level master page is obliterated.

Any way to do this?

i'm struggling to find a solution to this same problem as well. in the year or so since you asked, did you ever find a convenient way to do this? — Funka
– Funka, Commented Sep 15, 2011 at 20:22
Not really. The nested placeholder solution works well, though it's obviously ugly. I've sinced move to the Razor view engine, which has a much nicer system for optionally rendering page sections, replacing content only when you want, etc. — 3Dave
– 3Dave, Commented Sep 20, 2011 at 18:26

ten5peed · Accepted Answer · 2010-08-19 20:07:02Z

1

I can't think of any way other than having the following in your child master page

<asp:Content ContentPlaceHolderID="SearchFormContent" ID="SearchFormContentContainer" runat="server">
    <asp:ContentPlaceHolder ID="SearchFormContent" runat="server">
        <%Html.RenderPartial("SearchFormControl"); %>
    </asp:ContentPlaceHolder>
</asp:ContentPlaceHolder>

Nasty I know, but its the only way I can think of when using master pages.

HTHs,
Charles

answered Aug 19, 2010 at 20:07

ten5peed

15.9k3 gold badges62 silver badges74 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

3Dave Over a year ago

I'd hate to have to duplicate that all over the place. We're talking about quite a few pages.

ten5peed Over a year ago

Quite a few master pages you mean? Because you only have to do it in the (child) master pages.

3Dave Over a year ago

Two years and a full redisign and migration to Sitefinity later, thus actually makes sense.

BritishDeveloper · Accepted Answer · 2010-08-19 19:54:57Z

1

Remove all your ContentPlaceHolders and leave the SearchFormControl directly on the site.master. If you never want to override the SearchFormControl then you don't need to define the ControlPlaceHolders

answered Aug 19, 2010 at 19:54

BritishDeveloper

13.4k9 gold badges54 silver badges62 bronze badges

2 Comments

3Dave Over a year ago

The problem is that I DO want to override the SearchFormControl content. It is rendered differently in a few different areas of the site, but some areas need to use the default content from the top level site master page.

John Farrell Over a year ago

@David Lively - Based on your two comments it sounds like you want your cake and to eat it too.

Stéphane · Accepted Answer · 2010-08-19 20:15:45Z

1

you can put content in the contentPlaceHolder on the masterpage. that will be rendered by default if you don't override the with a content on a child page.

answered Aug 19, 2010 at 20:15

Stéphane

11.9k7 gold badges51 silver badges63 bronze badges

1 Comment

Adi Over a year ago

When I add a new "Web Form using Master Page" the designer will override all place holders found in master page. Is there a way to tell not to override one of them?

Collectives™ on Stack Overflow

ASP.NET MVC nested master pages, inherit content

3 Answers 3

3 Comments

2 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

3 Comments

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related