Documentation about App Config files confusingly spread across multiple application sections

[greyseal96]

To find information about app config files, I have had to read through at least four different application sections on docs.microsoft.com (and there may be more that I haven't found; I don't know...):
--Visual Studio: https://docs.microsoft.com/en-us/visualstudio/ide/managing-application-settings-dotnet?view=vs-2019
--Windows Forms: https://docs.microsoft.com/en-us/dotnet/framework/winforms/advanced/application-settings-architecture
--ADO.NET: https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/connection-strings-and-configuration-files
--.NET Framework (this one)

This has been sort of a pet peeve of mine for years now; even back to the MSDN documentation. docs.microsoft.com has been such a big improvement that I'm wondering now: Why can't all of these sections be combined and unified in one easy to find place? App Config files is one of those things that I don't do often enough to keep it in my memory so, when I need to refresh my memory, it's always a scavenger hunt to find all of the documentation to remember how thing go together. Is there any way that they can all be put in one place? I know that they affect all four of those products but I have to imagine that there's got to be an easier way to organize the info so that it's easy to find quickly. It would be a huge help for me and I think it would be helpful for others as well. Thanks for your consideration.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b39c5030-7cdb-a2b4-4abf-0451ab4d8de4
• Version Independent ID: 4aae87fd-84b4-4cbf-aeec-4da9a43f4396
• Content: Configuring Apps by using Configuration Files
• Content Source: docs/framework/configure-apps/index.md
• Product: dotnet-framework
• GitHub Login: @dotnet-bot
• Microsoft Alias: dotnetcontent

[Thraka]

@greyseal96 Thank you for pointing this out. That is highly annoying and is really just an artifact of different products writing documentation covering the same scenario.

I'm going to add this to our backlog of work. We're coming back through and updating the windows forms articles so when that happens it will be a good opportunity to reduce the content covering this scenario.

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.