asp.net - .NET 4 web.config file refactoring - what's the value? -


according what's new in .net 4: "major configuration elements have been moved machine.config file, , applications inherit these settings."

i'm on project upgrading .net 3.5 .net 4, , have questions change:

  • i assume change optional: if leave current web.config file as-is, should run fine under .net 4 - correct?
  • this enhancement seems have dubious value: config hasn't been simplified - complexity/bloat has been relocated machine.config file instead of web.config. missing something?
  • it seems enhancement makes deployment more difficult: in addition deployment steps had, need modify machine.config file ensure contains our expected settings/values.

as can see, initial take on is: it's hassle , don't want it. there perspective i'm missing makes change useful , valuable?

edit: nathan , rob - both answers helpful , appreciated - difficult decide flag "real" answer. upvoted both, of course. again!

you don't ever need modify machine.config unless want settings default applications running on server.

most of moved out of web.config "boilerplate" config items added release of .net 3 , 3.5. needed asp.net register controls, handlers, etc, things need modify, or care to.

so useful because configuration items "white noise" moved out of way, allowing focus on settings want manipulate.

scottgu discusses subject in blog post of his: http://weblogs.asp.net/scottgu/archive/2009/08/25/clean-web-config-files-vs-2010-and-net-4-0-series.aspx


Comments

Popular posts from this blog

apache - Add omitted ? to URLs -

redirect - bbPress Forum - rewrite to wwww.mysite prohibits login -

php - How can I stop spam on my custom forum/blog? -