Hi,
I see your point. Well in principle I would...

2009-04-12T19:43:00.000+02:00

Hi,
I see your point. Well in principle I would say that if these settings are related to the environment where the application resides (e.g. dev, staging, production) then it would also make sense to have them in a different file.
But of course I completely agree with you when you say that if you open the web.config that you immediately want to see all of the configuration at a glance and not follow links to references setting files. Also having different configuration files is somewhat dangerous since it quickly may become nasty and difficult to maintain. The less config files you have the better it is.
The risk you have with the single, "manually managed" web.config is just that you may make changes locally, commit it to the repository, but then your team colleague publishes the app the next morning, without having recognized your changes..

From a "correctness" point of view I would say that having environment-related settings in different files would make sense, however I think it also very much depends on ones specific needs and also preferences.

We are using this approach for our connection stri...

2009-04-11T01:51:00.000+02:00

We are using this approach for our connection strings as well. But we have to many different other settings between dev, staging and production...
So we still have 3 web.config files. But we need to deploy manual steps only if we change something in them.

What would you suggest if you have a lot of different settings?

E.g. Move all of these in separate file?
<setting name="DefaultFromAddress" serializeAs="String">
<value>X@X.com</value>
</setting>
<setting name="CloseDate" serializeAs="String">
<value>03/31/2009 23:59:00</value>
</setting>
<setting name="OpenDate" serializeAs="String">
<value>03/02/2009 23:59:00</value>
</setting>
<setting name="NRMABCCAddress" serializeAs="String">
<value>XX.XX@X.com.au</value>
</setting>
<setting name="GlobalExceptionMailTo" serializeAs="String">
<value>xxxxx@ssw.com.au</value>
</setting>
<setting name="ReportService"
serializeAs="String">
<value>http://XXXX:80/ReportServer/xx.asmx</value>
</setting>
<setting name="GlobalExceptionMailToAdditional" serializeAs="String">
<value>xxxxx@ssw.com.au</value>
</setting>

What I don't like about that, If I open web.config I want to see immediately whats going on, without opening other files.

Comments on Juri's TechBlog: Best practices: Deploying webapps (contd.)

Hi,I see your point. Well in principle I would...

We are using this approach for our connection stri...

Hi,
I see your point. Well in principle I would...