Let me start by saying that this is a new and first time deployment of TFS with 0 experience in Visual Studio as an added bonus. I managed to install everything, and I am very happy to say that I can even deploy it as part of the build process in our different intermediate environments, but this is where things went south.
I am trying to set up separate build definitions for each development phase so that I can take advantage of configuration transformations and use granular permissions for those who receive ads. In the configuration manager, I configured it so that each solution configuration displays a display of 1-1 in the context of the project and always builds "Any processor." The problem is that when I use the / p option: Configuration = QA in the MSBuild arguments or just point it to "Items to build"; section of the build process parameters, build failure with a warning, and does not seem to reach MSDeploy.
Using the following arguments in MSBuild, I deploy with the default setting, but again, there is no love in specifying the configuration.
/ p: DeployOnBuild = True / p: DeployTarget = MSDeployPublish / p: MSDeployPublishMethod = WMSVC / p: MsDeployServiceUrl = 10.31.60.109 / p: username = tfsdeploy / p: password = lulz / p: DeployIISAppPath = Bob
Here is the warning I get in the TFS build explorer when specifying the configuration used.
C: \ Builds \ 2 \ Bob \ Bob - final test \ Sources \ Bob \ Bob.sln.metaproj: The specified configuration of the solution "QA | Any CPU" is invalid. Specify the correct solution configuration using the Configuration and Platform properties (for example, MSBuild.exe Solution.sln / p: Configuration = Debug / p: Platform = "Any CPU") or leave these properties empty to use the default solution configuration.
VS2008, VSS VS2008, TFS2010, VS2010, MS /.
.