My website contains lot of configuration items (Key/Value pair) in mutliple web config (for various modules)..Whenever there is any change in configuration, people who works in a team enviornment asked to update the config files as part of their requirement..
But somehow we missed to collate all the changes made in config files while deploying into production. So which is the best way to handle web config changes across projects in team environment. Thanks in Advance.
Are you using any source repository like TFS, SVN ,CVS,
if yes then ask your programmer to commit the changes after merging with SVN code or CVS code. and when you are going to deploy the final build just use the latest copy of build.
web.confgasp.net
Mark the reply if it resolved your query :) Thanks - Rajat Jaiswal | Blog
Member
3 Points
9 Posts
Web config Management
Oct 14, 2013 06:41 PM|balaece603010|LINK
My website contains lot of configuration items (Key/Value pair) in mutliple web config (for various modules)..Whenever there is any change in configuration, people who works in a team enviornment asked to update the config files as part of their requirement.. But somehow we missed to collate all the changes made in config files while deploying into production. So which is the best way to handle web config changes across projects in team environment. Thanks in Advance.
web.confg asp.net
Participant
1351 Points
482 Posts
Re: Web config Management
Oct 14, 2013 10:28 PM|Rajat|LINK
Are you using any source repository like TFS, SVN ,CVS,
if yes then ask your programmer to commit the changes after merging with SVN code or CVS code. and when you are going to deploy the final build just use the latest copy of build.
web.confg asp.net