At some point, you would type in the true target folder that would go into the batch file as the root of the target paths for the XCOPY and DEL commands. It could take any Folder Sync command, and instead of actually performing it, copy all the files to a new folder and create a batch file to deploy them and plus delete the "right side orphaned" files. I would love it if BC did something like this for me. And I only need individual file commands to delete the orphans that no longer belong on the server. Then my batch file simply copies the entire folder over to the server. Instead, I loaded my folders in BC, showed only differences, then used the Copy to Folder to create a "patch" of just the new or changed files into a new folder. I ended up not even bothering with individual files for the XCOPY. I used the Folder Comparison Report to list out the changed and deleted files, then I used some Search/Replace in a text editor to turn the lines into batch commands. Today I created such a batch file by hand. Instead, it would be ideal if we could generate batch files that use XCOPY and DEL to take all the changes from the local folder and commit them to the target server. However, it would be nice if we could eliminate the need to use BC for the final step. He takes the merged version, then simply uses Folder Sync with "Mirror" mode to copy all the new/changed files, and delete any removed files from the server in one shot. We then use BC again to perform the actual deployment (done by another person). We examine the current source, compare it to what's in production, and produce a new version of production to deploy. ![]() If you omit the /NDL option, it is necessary to include the /FP option if you want full paths listed for each file.At my workplace we use Beyond Compare to deploy Asp.net web sites.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |