Images

Eeyore · November 7th, 2009, 09:45 PM

This is the new error that I'm getting but it's not in VWD. It's in the browser when I try to load my default page.

Code:

Server Error in '/' Application.
Content controls have to be top-level controls in a content page or a nested master page that references a master page.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Content controls have to be top-level controls in a content page or a nested master page that references a master page.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): Content controls have to be top-level controls in a content page or a nested master page that references a master page.]
   System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection) +8668328
   System.Web.UI.Page.get_Master() +51
   System.Web.UI.Page.ApplyMasterPage() +15
   System.Web.UI.Page.PerformPreInit() +45
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +282

I'm not sure how to find my error from this Stack Trace. My guess would be that the issue is in one of the CodeBehind files because the Stack Trace looks like code that I may have seen in those files before. It looks to me like the browser is having trouble merging the master page and the default page. Am I on the right track or am I not making any sense at all?

The good news is that I finally see the default page inheriting things from my master page and I'm no longer getting any errors.

Imar · November 8th, 2009, 03:56 AM

Hi there,

First of all, the browser doesn't merge anything. The browser simply requests a page and then the *server* merges the master and content pages and sends the resulting HTML to the browser. The browser doesn't understand anything about ASP.NET and only works with HTML. CSS, JavaScript and other client resources.

The error you get is because your content page contains other code than the <asp:Content> controls. You get this error when your content page contains, for example, plain HTML or server controls outside the content controls like this:

Code:

 
<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>
<asp:Label id="somelabel" runat="server" />
<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">
</asp:Content>

Notice how in this example the label is placed outside the content controls.

Remove everything from the page that is not inside a Content control (except the @ Page directive) and the error should go away.

Hope this helps,.

Imar