As web.config elements is increasing so far, i recommend making a complete GUI to deal with it.
Cameron Usman commented
Maybe it just needs a Smart Text Editor (WebMatrix and Visual Studio) that is aware of all the possible web.config XML tags, grouping / wraps, attributes, and possible values where sets apply. The "Editor" should also have ability to encrypt password and do other such things. The "Editor" should also allow quick reference to full documentation of all the web.config supported XML including deprecated and version specific information.
Michael Paterson commented
Personally I find the editors more complex than learning the XML.
When I first saw the reduced clutter web.Config in ASP.NET 4 I was really impressed. Then I saw what it still looks like to support and MVC project...
Everything still looks like its heading in the right direction and I don't know if a full on GUI is the way to to, but I think this could still use some attention/improvement.
Jonathas Sucupira commented
It would be great if there was a tool like WCF service configuration editor to manage web.config
Scott Hunter commented
Yes, we simplified the web.config in .NET 4 and with .NET 4.5 being a framework that replaces .NET we had to add some flags to the config in order to add new features but allow them to be disabled for applications targeting .NET 4. We will again reduce this again when we have a release that does not replace your existing framework.
Mauricio Scheffer commented
Instead, I'd solve the real problem, which is having complex web.config files in the first place. Microsoft already started simplifying this a few years ago: http://weblogs.asp.net/scottgu/archive/2009/08/25/clean-web-config-files-vs-2010-and-net-4-0-series.aspx