To be able to configure the default behavior of the 'Include Dependencies' check box
When you create a new project and do a deployment for the first time the 'Include Dependencies' check box is set to true. Can this default behaviour be changed to false ?
Can the user have the option to set the default behaviour
Todd Harry commented
I've up-voted this... our shop has made a rule to never deploy dependencies, and the default behavior is to have the box checked in SQL Compare's Deployment step "3 - Review dependencies". We'd prefer to have an Application Option that turns this default value on/off, instead of having to remember to turn it off every time we setup a new deployment.
I have had several issues pertaining to this. A while back, I was doing a deployment and only wanted to deploy my changes to our remote DB, and the box was checked making me overwrite a co-worker's changes he had made by accident. Just now I almost lost weeks of work due to the dependencies box being checked and overwriting all of my changes I had made locally while trying to retrieve a couple of my co-worker's changes from our remote DB. Thankfully I had a backup, but I should not have to make sure this box is not checked because it is the default behavior, we should be able to configure it ourselves so that we can choose the default to be unchecked and not deploy the dependencies.
This has been an issue for our company several times as we never use 'Include Dependencies'. Since our established projects are all set to false often times people don't pay close enough attention to this screen which ends up causing deployment issues.