[Mono-bugs] [Bug 371663] New: ASP.NET Masterpages broken in mono-1-9 and trunk

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Mar 17 03:40:01 EDT 2008


https://bugzilla.novell.com/show_bug.cgi?id=371663


           Summary: ASP.NET Masterpages broken in mono-1-9 and trunk
           Product: Mono: Class Libraries
           Version: 1.9.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: tyler at monkeypox.org
         QAContact: mono-bugs at lists.ximian.com
          Found By: Third Party Developer/Partner


Created an attachment (id=202480)
 --> (https://bugzilla.novell.com/attachment.cgi?id=202480)
Actual masterpage file

According to eno, around Jan 24th there were changes to the rendering of
Masterpages in Mono's ASP.NET implementation

02:06 < eno> rtyler: are you looking for blamestorming? :)  As I've spotted,
the failure point is likely BuildManager introduction.
02:07 < rtyler> eno: nah, it's just weird to me


Sites running ASP.NET Masterpages throw the following errors on load:


Failed to create MasterPage instance for 'Urlencode.masterpage'.

Description: HTTP 500. Error processing request.

Stack Trace: System.Web.HttpException: Failed to create MasterPage instance for
'Urlencode.masterpage'.
  at System.Web.UI.MasterPage.CreateMasterPage (System.Web.UI.TemplateControl
owner, System.Web.HttpContext context, System.String masterPageFile,
IDictionary contentTemplateCollection) [0x00000] 
  at System.Web.UI.Page.get_Master () [0x00000] 
  at System.Web.UI.Page.ApplyMasterPage () [0x00000] 
  at System.Web.UI.Page.InternalProcessRequest () [0x00000] 
  at System.Web.UI.Page.ProcessRequest (System.Web.HttpContext context)
[0x00000] 

Attached is a masterpage and Default.aspx that are throwing errors


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list