For the workflow, I propose a code promotion model.
Inside TFS, you have the idea of creating quality. SO, when you initially check the code in the assembly, it starts with a quality saying “ready to test,” if the assembly passes, testers can decide when they want to take the assembly for testing, when they check the assembly, they can mark it as “ready for deployment, you can use these realeas for deployment.
If nothing has changed in TFS 2010, you need to run your own implementation for deployment. We used the MS assembly to create the MSI using Wix, and then the testers tested the deployment process for us.
Take a look at the following msbuild extensions to help deploy in test / live environments:
I would recommend that you spend a little time on the assembly process and get it at the expense of water, there is nothing more embarrassing that deploying a release for life will not work, and the client will lose faith in it.
source share