G
Guest
Hi, I am confornted with a problem regarding web.config file. I have 4
environements (Dev, Test, staging and production). The IT people need
wgenever a new MSI delivered to have the right environment keys in there
sections and not the dev machines web config. What I mean by that I don't
want the IT people to edit the web config for each environement manually. Is
there any baset practices or patterns to automatically deploy goof web.config
files.
I use TFS for nightly builds and thinking of implememnting TFS a s the tool
which should be used by IT people to get delivarables in order to deploy them
instead of filling special froems and using files shares for delivarables.
Of course, I know that we can exclude the web.config from the msi and every
delivery people go and update manullay the file in another environment but I
dont want that either if possible of course.
Thanks.
environements (Dev, Test, staging and production). The IT people need
wgenever a new MSI delivered to have the right environment keys in there
sections and not the dev machines web config. What I mean by that I don't
want the IT people to edit the web config for each environement manually. Is
there any baset practices or patterns to automatically deploy goof web.config
files.
I use TFS for nightly builds and thinking of implememnting TFS a s the tool
which should be used by IT people to get delivarables in order to deploy them
instead of filling special froems and using files shares for delivarables.
Of course, I know that we can exclude the web.config from the msi and every
delivery people go and update manullay the file in another environment but I
dont want that either if possible of course.
Thanks.