VB.NET App.config values resolving differently in production: machine.config inheritance or stale My.Settings defaults?
In a .NET Framework Visual Basic project, App.config is copied to [AssemblyName].exe.config at build time, and runtime reads go through ConfigurationManager (appSettings, connectionStrings) or the My.Settings proxy generated by the Project Designer. A value that resolves one way on a developer machine can resolve differently on a production server, and sever
visualbasic