[Mono-bugs] [Bug 495957] New: bundled machine.config files no longer work

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Apr 17 09:52:18 EDT 2009


           Summary: bundled machine.config files no longer work
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Configuration
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: tlillqvist at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---

After the change to System.Configuration.Configuration.Load() (in
mcs/class/System.Configuration/System.Configuration/Configuration.cs) that
added a test for file existance before attempting to read it, using a bundled
machine.config file (as indicated by passing the --machine-config file to
mkbundle2) no longer works.

The pathname for the machine.config file that the upper levels have constructed
is rather random in a bundled executable, and does not exist, nor is it
supposed to exist. The whole point of using a bundled executable with a bundled
machine.config file is to have a freestanding executable that doesn't open any
config files at run-time.

It seems to work fine to just restore the code to what it used to be in 1.2.6.
Then the code in
System.Configuration.InternalConfigurationHost.OpenStreamForRead() (in
InternalConfigurationHost.cs) that calls get_bundled_machine_config() does what
it is designed to to, i.e. in the case of a bundled executable with a bundled
machine.config file, returns the contents of that instead.

Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list