Databases
StackOverflow2013
Postsdbo
POTeam Foundation Server build is transforming web.config TWICE, and the second time is wrong
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTeam Foundation Server build is transforming web.config TWICE, and the second time is wrong
    primarykey
    data
    text
    <p>I have a TFS build definition set up with the following information in the Process -> Advanced -> MSBuild Arguments section: (the [] bracketed values are omitted in this post for security)</p> <pre><code>/p:DeployOnBuild=True /p:MSDeployPublishMethod=RemoteAgent /p:MSDeployServiceUrl=[URL] /p:DeployIisAppPath=[IISPATH] /p:UserName=[USERNAME] /p:Password=[PASSWORD] /p:CreatePackageOnPublish=True /p:DeployTarget=MSDeployPublish /p:Configuration=Development </code></pre> <p>Here's the issue I have. I have many configurations set up in my web project, and the Development configuration is one of them. If I leave off the "/p:Configuration=Development" and build the project, which then auto-deploys to our dev environment, the web.config transform is wrong. It's replacing my connection string info with the information from another configuration.</p> <p>If I put the "/p:Configuration=Development" back into the MSBuild arg list and open the web.config file in VS2010 during the build process, the first time the web.config is changed outside my IDE, I can see that the appropriate web.config transform has been made in accordance with the Development configuration, but then the web.config file is changed AGAIN, and it's back to the improper configuration.</p> <p>My thought here is that when leaving the "/p:Configuration=Development" on, MSBuild is getting it right, but whatever process that is called from MSBuild (I'm assuming MSDeploy) to actually deploy the site to the server is getting it wrong.</p> <p>Oh, and I'm using an IIS6 server, not IIS7, so any IIS7-specific functionality won't really help me.</p> <p>Any ideas here of how to fix this problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJohn Saunders
    1. USMichael McCarthy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTeam Foundation Server build is transforming web.config TWICE, and the second time is wrong
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs it wrong after deployment or before? The transformed config in the drop folder does not include connection string transformations. They are left as MSDEPLOY parameters.
      singulars
      1. POTeam Foundation Server build is transforming web.config TWICE, and the second time is wrong
      1. USJohn Saunders
    2. COJohn, so when in the process do the connection string transformations happen? As part of the MSBuild process, or during the call from MSBuild to MSDeploy? FYI, I'm relying on the .cmd file generated via TFS Team Build, plus the MSBuild Args above that are set in the MSBuild Arguments location in the build definition.
      singulars
      1. POTeam Foundation Server build is transforming web.config TWICE, and the second time is wrong
      1. USMichael McCarthy
    3. COIt happens during msdeploy. Actually the transformation has already taken place but for connection strings the result is in the parameters.xml file. Please answer whether the transform is wrong _after_ deployment.
      singulars
      1. POTeam Foundation Server build is transforming web.config TWICE, and the second time is wrong
      1. USJohn Saunders
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload