Right now some of the global settings are only manageable from the VS options dialog which means that all the team members need to sync up manually. This problems worsens the more projects a person works on.
What i would love is to always have an *.mwsettings file (and decouple it from the project file) that also allows the overriding of the global settings.
This way each project/solution can be configured by one person and the settings shared with all the teammates.
Ideally this feature looks for a *.mwsettings file both at the root of the project and the solution.
|
Status: New
|
|
Will it include the settings for which files are merged together? I believe it would be very useful if we could define the files to be merged together (like the /i:files) within a configuration file as well, and the command line could read this configuration file to compile all files which are part of the project. Also the CI could run the very same command line. Thanks |
|
|
|
|
|
Seems to me that the project file is absolutely the best place to store these settings – not in a decoupled file. People that use an MSBuild approach would, potentially, need to interrogate a secondary file (which is fun at the best of times, whereas interrogating settings from the Visual Studio project files is straightforward) in order to get their settings in order. |
|
|
|
|
