You can create a directory structure in which you store CM and CD files. The following is an example directory structure
--- App_Config
----- Enable
-------- zConfig
----------- CM Config
----------- CD configuration
Then you can create an assembly script that takes into account the assembly configuration (debugging, release). From this, when you build your decision, he will know what configuration to take.
I would suggest defining a new build configuration to minimize the risk of confusion. For example, create 1 for CM and 1 for CD
This is an example of what my build script looks like in my solution
if %Configuration% EQU DEBUG ( if exist %SolutionDir%..\..\Website\App_Config\Include\ABBs\UAT RMDIR /S /Q %SolutionDir%..\..\Website\App_Config\Include\ABBs\UAT if exist %SolutionDir%..\..\Website\App_Config\Include\ABBs\PRODCluster1 RMDIR /S /Q %SolutionDir%..\..\Website\App_Config\Include\ABBs\PRODCluster1 if exist %SolutionDir%..\..\Website\App_Config\Include\ABBs\PRODCluster2 RMDIR /S /Q %SolutionDir%..\..\Website\App_Config\Include\ABBs\PRODCluster2 if exist %SolutionDir%..\..\Website\App_Config\Include\ABBs\PRODCluster3 RMDIR /S /Q %SolutionDir%..\..\Website\App_Config\Include\ABBs\PRODCluster3 )
It will copy the configuration file from my solution to the path \ Website \ App_Config \ Include \ ABBs \ PRODCluster1 if my Debug assembly configuration
source share