Do you create a Continuous Integration Build for the Solution?
Updated by Brady Stroud [SSW] 1 year ago. See history
(Before you configure continuous deployment) You need to ensure that the code that you have on the server compiles. A successful CI build without deployment lets you know the solution will compile.
Figure: The Build definition name should include the project name. The reason for this is that builds for all solutions are placed in the same folder, and including the build name makes the Build Drop folder organised
Figure: On the Trigger tab choose Continuous Integration. This ensures that each check-in results in a build
Figure: On the Workspace tab you need to include all source control folders that are required for the build
Figure: Enter the path to your Drop Folder (where you drop your builds)
Figure: Choose the Default Build template and enter the DeployOnBuild argument to the MSBuild Arguments parameter of the build template
Figure: Queue a build, to ensure our CI build is working correctly
Figure: Before we setup continuous deployment it is important to get a successful basic CI build