I wondered if anyone could help.
We have a large solution which contains multiple components (2 web sites and various services).
The same solution is used to deploy 5 different 'projects'. This is handled via different config files and various XML transformations as part of the build process. We also have multiple environments that we deploy to (Alpha, QA, Beta etc). Each project is basically a geo-location version of a web site with different features etc.
We have a configuration setting for each project/environment pair, e.g. ProjectA-Alpha, ProjectA-QA, ProjectA-Beta, ProjectB-Alpha etc.
In deployment manager we have had to set up a single environment for each project/environment pair so that the configuration transformations happen correctly. This means that Project A deploys to ProjectA-Alpha, ProjectA-QA etc, even though they are the same target machine (e.g. IIS-1, SVC-1 and SVC-2 for example).
What would be really helpful is if there was a way to overwrite the configuration transformation setting as a variable, or to be able to update the RedGateEnvironmentName as part of the release.
We are currently adding Project 5 to the mix, meaning we have 5 projects and hence 15 environments (Alpha, QA and Beta for each), even though we only have 3 actual target machines.
Anyone any ideas on how we might manage this, or if this could be added as a new feature to deployment manager?