One thing you could do for the production deployment is package the web site as a MSI (using WiX for example) and put that in a drop location that the prod server can pull from and execute with msiexec silently. Depending on your environment, the web site probably does not have anything sensitive in it, so a post-build task can drop ithe MSI on an FTP site and your web server can pull it from there and open it.
From: [email protected] [mailto:[email protected]] On Behalf Of Oscar Bautista Sent: Tuesday, May 18, 2010 9:39 AM To: ozTFS Subject: Configuration Set Up Question Good morning TFS team. I have a general question. We have developed custom build/deploy processes for our DEV, QA, and PROD environments. We use TFS Web to deploy to each environment accordingly. We created a TFSSERVICE domain account that the web app uses. Everything plays nicely. DEV and QA are in the Domain. PROD Web Tier is inside a DMZ (not joined to the Domain). When we deploy to PROD we manually copy files to the Web Server since TFS Web App uses a domain account that the Web Server does not recognize. Is there a way we can use TFS Web App to deploy to our PROD Web Server? Do you suggest we create local accounts on all servers using the same credentials and run TFS Web App using a local account with same credentials? Any feedback or suggestions are very much appreciated. Thank you in advance for your thoughts, Oscar Bautista
_______________________________________________ oztfs mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
