[Mono-bugs] [Bug 80997][Nor] Changed - [2.0] DbProviderFactories does not use ConfigurationManager
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Sat Mar 3 07:46:56 EST 2007
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 gert.driesen at pandora.be.
http://bugzilla.ximian.com/show_bug.cgi?id=80997
--- shadow/80997 2007-03-03 00:36:50.000000000 -0500
+++ shadow/80997.tmp.1481 2007-03-03 07:46:56.000000000 -0500
@@ -4,20 +4,20 @@
OS: unknown
OS Details:
Status: NEW
Resolution:
Severity: Unknown
Priority: Normal
-Component: Configuration
-AssignedTo: mhabersack at novell.com
+Component: Sys.Data
+AssignedTo: gert.driesen at pandora.be
ReportedBy: mmorano at mikeandwan.us
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
URL:
Cc:
-Summary: web.config sections are not processed
+Summary: [2.0] DbProviderFactories does not use ConfigurationManager
Description of Problem:
When trying to port a web application from MS to mono, I ran into a problem
when I was trying to specify the provider information for a MySql database
in the web.config, via a system.data configuration section. After adding
the configuration pieces, it still was not finding the class as I expected.
@@ -89,6 +89,14 @@
included in bug report)
Moved from System.Web -> Configuration
Thanks,
Mike
+
+------- Additional Comments From gert.driesen at pandora.be 2007-03-03 07:46 -------
+Apparently, the problem is that DbProviderFactories uses the
+ConfigurationSettings class instead of ConfigurationManager. The
+ConfigurationSettings class does not allow attributes on the
+configuration node.
+
+I'll probably submit a separate bug report for that.
More information about the mono-bugs
mailing list