Visual Studio 2015 adds a file named .vsconfigapplicationhost.config
to the root of a solution when an ASP.NET Web application project is created.
Should this file be checked in to source control or should it be ignored (so that each user will have their own local copy)?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
You should ignore .vs folder all together.
However, there are cases where you want to persist some config on your applicationhost.config file such as registering FQDN as explained here.
For this type of config, you want to use the global application host file where you can persist your changes.
In a classic Web Application project (where you have .csproj file), you need to set the UseGlobalApplicationHostFile property to true inside the .csproj file:
<UseGlobalApplicationHostFile>True</UseGlobalApplicationHostFile>
VS 2015 honors this and uses the global application host file. However, there is no way to tell ASP.NET 5 projects to look for this today as far as I know.
Method 2
If you need custom configuration for IIS Express (example), add the file to source control so that it is shared with the team. If not, you can exclude this file, and VS2015 will recreate it as needed.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0