Bug 26398 - app.config Build Action does not reflect special processing
Summary: app.config Build Action does not reflect special processing
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Lluis Sanchez
Depends on:
Reported: 2015-01-25 16:11 UTC by John Lyon-Smith
Modified: 2015-03-09 07:10 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 on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description John Lyon-Smith 2015-01-25 16:11:21 UTC
The app.config file is treated specially by the build system and this is not reflected in the Properties panel.  It merely indicates that the "Build Action" is None and "Copy to output directory" is "Do not copy".  In fact the file _is_ copied to the output directory and is renamed $(TargetName).exe.config.  Also, if either "Build Action" or "Copy to Output Directory" you break this behavior.  This behavior is "magical" and confusing, especially if you are not familiar with Visual Studio or .NET.

Suggested fix: a special Build Action call "Configuration" that disables other options and reflects this special processing.
Comment 1 Lluis Sanchez 2015-03-09 07:10:15 UTC
I agree it is a bit confusing, but unfortunately we can't change this behavior since it would break compatibility with Visual Studio.