If I have projects that are deployed by copying files (executables, dll’s and data files) to their destination folder, is it correct that I can ommit copying the app.config-file (executableName.config) because it will created anyway on the first app startup per user in the users local storage?
Or otherwise asked, is it right, that the app.config (executableName.config) in the exeutables directory /bin/debug or /bin/release is only for debuging purposes there and could be deleted without any implications?
I have tested and used this without problems so far (deleting and not deploying the config file) but maybe there exist some side effects that are not obvious at the first glance?
My understanding from this article is the [AppName].exe.config file will be merged with the other configuration files (eg Machine.config, User.config) when configuration is requested by the code.
Thus, if you don’t have any configuration and choose to omit the exe config you shouldn’t have any issues.
The exe config is not used for debugging purposes.