I was shocked too about this: At VS2019, saving files in PHP Project published file at Save directly to the production server! Luckily I was alert enough to notice and react to VS console output reporting successful publish, and was able to revert the change to the production server from local production backup image immediately, so no harm was done. Need a way to disable this! As a workaround, I set up a local temp dir and created and activated a new Publish profile named "dummy" targetting to the temp dir. Now at least this "forced immediate publish per file at save" feature does no harm to my production. Still need a neater solution to this, please.