Bug 10155 - Configuration.SaveAs does not save external files in the correct directory
Summary: Configuration.SaveAs does not save external files in the correct directory
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: master
Hardware: All All
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-02-08 05:06 UTC by Sven Groot
Modified: 2013-02-08 05:06 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 10155 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Sven Groot 2013-02-08 05:06:24 UTC
When using Configuration.SaveAs to save a configuration file to a different directory, any external XML files (configuration sections for which the ConfigurationSection.SectionInfo.ConfigSource property is not null) should be written to the same directory as the main config file (this is the behavior of Microsoft .Net).

Instead, Mono writes the external files to their original locations, relative to the configuration file from which the configuration was loaded, rather than the one to which it is being saved. 

This means that when attempting to load the configuration back later, it will fail because the external files are not found (since when loading it will look for them relative to the main file).