|
-
Aug 2nd, 2010, 06:21 AM
#1
Thread Starter
Fanatic Member
Master web config
Guys,
We have a deployment with 4 web.config files that need editing to get from development environment to live/test.
I am looking for a method of centralising the lines that need changing in the web.configs into a master file. I know you can do this within app.settings using the "file=" attribute of the appSettings section... but is there a way to do this with the other settings without changes to code?
The connection string is another example. I could ask the developers to recode any of these variables into app.settings, but there are things suchs as these that I dont think are editable...
<client>
<endpoint address="http://1.1.1.1/Test.Part1.Securities/SecurityService.svc"
Any suggestions please? So far, all install issues have been down to typos in all the web.config edits. Could I feasible direct the developers to put EVERYTHING configurable in the app.settings section then use the file redirect?
Bob
"I dislike 7 am. If 7 am were a person, I would punch 7 am in the biscuits." - Paul Ryan, DailyRamblings
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|