[Mono-bugs] [Bug 74180][Maj] New - XSP2: Wrong field names for controls when using master pages

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 29 Mar 2005 08:58:53 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by hchrholm@online.no.


--- shadow/74180	2005-03-29 08:58:53.000000000 -0500
+++ shadow/74180.tmp.3147	2005-03-29 08:58:53.000000000 -0500
@@ -0,0 +1,50 @@
+Bug#: 74180
+Product: Mono: Class Libraries
+Version: unspecified
+OS: SUSE 9.2
+OS Details: 
+Status: NEW   
+Priority: Major
+Component: Sys.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: hchrholm@online.no               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: XSP2: Wrong field names for controls when using master pages
+The following illustrates a problem with the current implementaion of 
+master pages in XSP2 (or the current 2.0 DLLs or wherever pages are 
+<%@ Page Language="C#" MasterPageFile="m.master" %>
+<script runat="server">
+  void Page_Load(object sender, EventArgs e) {
+    // the following line does not compile
+    //b.Text = "HAHA";
+  }
+<asp:Content runat="server" ContentPlaceHolderID="cph1">
+  <asp:Label runat="server" id="b" Text="b" />
+Steps to reproduce the problem:
+1. Create a master page m.master with a ContentPlaceHolder named cph1
+2. Create a page like the on above
+3. Run with XSP2
+Actual Results:
+The "b" Label control ends up as "protected Label _bctrl_10" in the
+page object. 
+Expected Results:
+In ASP.NET 2.0 Beta 1 and in XSP2 pages not using master
+pages, it becomes "protected Label b", as it should.