msbuild - c# compiler directives use in a continuous delivery pipeline -

my team uses compiler directives create different versions of our product different stages (debug, test, release) want move ci/cd strategy , discussing whether idea use compiler directives @ since artifact(s) produced 1 configuration cannot used another, example, our ci server runs build process test configuration , stages build process pass including ui automated tests, artifacts created in process cannot deployed production because production application needs compiled using release configuration creating new set of untested artifacts deploy production environment, which, in opinion makes work performed in previous stage(s) obsolete because want run tests against newly created artifacts.

has had similar similar situation , if how did address team. idea use c# compiler directives when want move ci/cd strategy?

we had similar problem 2 years ago. re-building our code each environment (dev, qa, mock, prod) , in cases check-ins occur between environments , invalidate our testing. when started our cd journey knew had build once/deploy many scenario. used msdeploy deploy our code. includes web sites/services, windows services, scheduled tasks , sql databases.

we place environment differences in our config files , control transformations via parameterization in msdeploy. parameterization applied @ deploy time. setup consists of parameters.xml file defines needs parameterized , setparameters.[environment].xml file each environment pertinent values enviornment.