c# - web.config best practices when upgrading -
i send out app , let customers make changes connection strings , such in web.config. when upgrade app causes annoyance because don't want overwrite values mine. this bad when versions of .net upgraded. how people typically handle type of situation? for example somehow split web.config out customer data no longer part of it? i've never heard of making web.config accessible , writable customers or other business folk. you're asking trouble. it sounds may want develop small front-end (web) utility allow them submit values in form , save database. have application access database these values, , not web.config. this seems more of content management issue.