[Mono-bugs] [Bug 77989][Wis] New - 2.0/xsp2 doesn't support custom config sections

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Sun Apr 2 11:27:35 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 joe_audette at yahoo.com.

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

--- shadow/77989	2006-04-02 11:27:35.000000000 -0400
+++ shadow/77989.tmp.31658	2006-04-02 11:27:35.000000000 -0400
@@ -0,0 +1,78 @@
+Bug#: 77989
+Product: Mono: Class Libraries
+Version: 1.1
+OS: SUSE 9.2
+OS Details: suse 10
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Sys.Web
+AssignedTo: gonzalo at ximian.com                            
+ReportedBy: joe_audette at yahoo.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: 2.0/xsp2 doesn't support custom config sections
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+It is possible on windows to setup custom config sections first with a
+declaration of the section like this:
+<configSections>
+		<sectionGroup name="system.web">
+			<section name="mojoEncryption"
+type="mojoPortal.Business.mojoEncryptionConfigurationHandler,
+mojoportal.Business" />
+		</sectionGroup>
+	</configSections>
+
+Then under the system.web section adding the custom section like this:
+<mojoEncryption>
+			<RSAKeyValue>
+			
+<Modulus>uckRHFWrxsDV+NR+oEK1csTkjic4E2byaUMV8FmTDhyzZMrDV3dJV8T00Esa+rgrlN08CCJC0epPyWGheI3KHgQmbq2iHak4Y67SHL0ZhRG7OHFFkITFSeVPQIqcinwk0PZfgbE239cM/0u7r9DQLIFTbRZKhd8fS//X7AsW3Js=</Modulus>
+				<Exponent>AQAB</Exponent>
+			
+<P>70rN3bB8CzW7iF5QEicDiGM5chkza5DxqRPVvXnnjejS2CAzlvzUdPSArjZUbupg4iaBJsN26TxwQ6OB99QrLw==</P>
+			
+<Q>xsHc6I+1yCxaPsqst/gDuKwPyutK3s7P2hfj6fIpNwmsvqxxMRAgPhw8mr3OK0yZjPRCZLCxBEVyoNEkB2paVQ==</Q>
+			
+<DP>5pz4+gX0Bfmq2inKkTP4O6Ek48lVvPzbaU8sVob9mc4gJRojngfb2TsqKLtDdAF9jXX+UhVerDkLGKSjxOw9EQ==</DP>
+			
+<DQ>dw5/XktfT3XJ5R0Qku6chA2FND73TTnC5dgzrNpi99XyxRCUiRgoyCuv3d1eVy9+NyHFd30ju/RBsrU0iMCbNQ==</DQ>
+			
+<InverseQ>6DNVGM4aB5jSXJgCYwwZdB6w09RofYWOi27g59k5+I1DC/VqgSo3QXY+dWK3qWReAYr2qAJJEhlRCvsou82d9Q==</InverseQ>
+			
+<D>mywXAIWFrcHOdcB16sEM8EkHZLvZGEt52PVRU6hdLQJHy72XHmzhc09r8rVoWVSOAg4uX9TN3qpH7bl/tkMnNjD9UCToIqQ+FF+TYL3+/irWEDqixujDeQAPEFCdYmviuRiMf7q3alBqF3Be39Fkbu/NJ75wgZKWmP1pE049abE=</D>
+			</RSAKeyValue>
+		</mojoEncryption>
+
+On mon this raises an error.
+
+
+Steps to reproduce the problem:
+1. register a custom config section as shown above
+2. 
+3. 
+
+Actual Results:
+System.Configuration.ConfigurationErrorsException: Unrecognized
+configuration section <mojoEncryption>
+
+Expected Results:
+no error should occur and the config section should be accessible to
+calling code
+
+How often does this happen?
+every time 
+
+
+Additional Information:
+not sure if I should be reporting things like this or not, whether its a
+bug or just not implemented yet. Chris Toshok asked in his blog what is
+needed in the 2.0 profile so I'm just entering errors I encounter with
+mojoportal trying to get it working under the 2.0 profile with some new
+features.


More information about the mono-bugs mailing list