Home/ Questions/Q 6704239
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T07:15:57+00:00

So we have a build process that handles different development web.configs across different environments.

  • 0

So we have a build process that handles different development web.configs across different environments. We use the ConfigSource attribute and have Team City pick the appropriate file.

That’s great, but what do I do when the developers have slightly different environments?

CI, can’t help, because everyones getting it straight out of SVN (i.e. CI obviously doesn’t build to each developers local machine).

I’ll use the ConnectionStrings config section as an example:

<connectionStrings configSource=".\Config\ConnectionStrings.config">
</connectionStrings>

And we have:
configs\ConnectionStrings.config (the generic one)

But I might need to use:

configs\ConnectionStrings.dev1.config
configs\ConnectionStrings.dev2.config
configs\ConnectionStrings.dev3.config

depending on which developer is using the code at the moment.

Any ideas?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Have you tried looking into web.config transformations? They might be able to provide the functionality that you seek while still keeping everything in version control or needing any code changes. Plus it will work for more things than just connection strings, but also directories, etc.

    • 0