Sorry if this is the wrong place to post this question as it seems to be more related to practices than patterns.
Managing different configurations between production and developments has been a problem that I’ve been confronted with in my last few jobs/projects. As the project grows, and things get fine tuned, these two configurations seem to diverge more and more. And
it consistently proved to be a problem during deployment processes.
There are the simple changes, like connection strings. But also more complex things like policy changes; where as exceptions may be blocked before reaching the user in production we may want them to propagate in development.
I was wondering if anyone has found a solution that they are happy with to create, deploy and maintain these filed over the life of a software product.
Thanks for any advice you may have,