What problems are arising that make you seek the web.config files out
I recently entered a full week of problem on Azure Web Site concerning Monitoring and cache.
(monitoring is set from a config file \config\hostcomponents.config and this file is not always used on AWS ?
and cache is not working, a reason could be a missing parameter in web.config ?)
As I was having no idea of the problem I started eliminating its possible reasons.
One question raised about the influence of all these web config: if you use 50 modules, you deploy more than 150 web.config files.
Then I noticed that some of them, in Orchard Core and Framework were containing different information.
From this point I started questioning myself on the influence of these files.
Bertrand told they are useless, so let's rip them out reducing the error factor.
For deployment I am using VS2012 publish and this process is spending part of its time
1) to adapt web.config for non debug and some other adaptations
2) deleting and copying web.config ... that had never changed, but as it changes them before comparing....
I also noticed that some VS2012 deployment settings have no influence on Orchard deployment, as for the debug file info which is always deployed if generated, whatever be the VS flag.
So I stared searching for info on what orchard is doing in the packaging process? is the VS publish packaging using what orchard has builtin for ?
I know that I have to dive into this code one day or another....
To come back to web.config: if we suppress them, we have less to maintain and deploy faster seems the conclusion.