[Mono-bugs] [Bug 78937][Nor] New - [2.0] GridView.Rows collection is not initialized after control creation

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Jul 24 09:02:47 EDT 2006


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 noaml at mainsoft.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78937

--- shadow/78937	2006-07-24 09:02:47.000000000 -0400
+++ shadow/78937.tmp.29459	2006-07-24 09:02:47.000000000 -0400
@@ -0,0 +1,41 @@
+Bug#: 78937
+Product: Mono: Class Libraries
+Version: 1.0
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.Web
+AssignedTo: gonzalo at ximian.com                            
+ReportedBy: noaml at mainsoft.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: [2.0] GridView.Rows collection is not initialized after control creation
+
+(copy of 78880)
+GridView.Rows collection is not initialized after control creation.
+
+Test case:
+MonoTests.System.Web.UI.WebControls.GridViewTest.GridView_DeleteItem
+
+Actual Results:
+null
+
+Expected Results:
+empty GridViewRowCollection
+
+
+
+
+------- Additional Comments From Andrew Skiba 2006-07-20 10:47 -------
+
+The same happens with DetailsView. To check why on dotnet Rows is not 
+null, I wrote test DetailsViewTest.EnsureChildControls, and found 
+that we have a difference in the flow. So in dotnet, when Rows is 
+accessed, protected override EnsureChildControls is called and 
+CreateChildControls is called (probably from 
+Control.EnsureChildControls).


More information about the mono-bugs mailing list