[Mono-bugs] [Bug 58686][Nor] Changed - MONO Beta 1 Bug: WebControlsConfig must implement IDictionary

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 19 May 2004 22:23:04 -0400 (EDT)

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 gonzalo@ximian.com.


--- shadow/58686	2004-05-19 07:54:26.000000000 -0400
+++ shadow/58686.tmp.13967	2004-05-19 22:23:04.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 58686
 Product: Mono: Class Libraries
 Version: unspecified
 OS: Red Hat 9.0
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: INVALID
 Severity: 004 Four hours
 Priority: Normal
 Component: Sys.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: davidandrewtaylor@hotmail.com               
 QAContact: mono-bugs@ximian.com
@@ -98,6 +98,47 @@
 of basic XML Documents (the component was released in Jan 2002 and is 
 used in a number of ASP.NET apps).  This particular component cast the 
 returned object to an IDictionary and by fixing this bug in MONO we will 
 fix the issue.
 Final Comment: Gonzalo makes me work hard for his affections :-)
+------- Additional Comments From gonzalo@ximian.com  2004-05-19 22:23 -------
+you can read:
+"Because the IConfigurationSectionHandler.Create method's return value
+is an Object type, you must cast the object to the type created by the
+section handler."
+So you must now the Type to do the cast. It makes no sense reading a
+configuration that other is handling and taking care of.
+It says, yes, this:
+"To read the settings from sampleSection, cast the object returned
+from ConfigurationSettings.GetConfig to an IDictionary object."
+But note that it says *sampleSection*, it's not establishing a rule.
+And it's talking about *custom* section handlers, not system section
+The second reference,
+has a nice title: "Custom Element for SingleTagSectionHandler"
+And, yes, for that case, we should return what SingleTagSectionHandler
+Same for the third one, dude, the title is "Custom Element for
+NameValueSectionHandler and DictionarySectionHandler". Those 2 must
+return what is stated in there, if not, it's a bug.
+Note that you're relying on an object returned by an internal and
+undocumented class. That will give you troubles.
+My question is why would someone want to read that using the
+configuration system? If you want to get the information, use Sys.Xml.
+How do you know what information must be in the IDictionary? (keys,