Can someone explain (better than technet / msdn docs) what the auto provider exactly does, how it works, and when to use it.
This applies to web deployment. I saw a lot of documentation defining -dest: auto, and that makes no sense to me.
The auto supplier indicates that the supplier at the destination will be the same as the source provider.
Example
msdeploy.exe -verb: sync -source: appHostConfig = "MySite" -dest: auto, namecomputer = Server1
The autoprovider avoids entering the full path for the -dest argument when the destination argument matches the -source argument. It also removes the need to copy the manifest file separately from the archive or package.
The provider automatically accepts the source you specify and uses the appropriate location on the destination computer. For example, if you specify appHostConfig = Site1 as the source, the destination on the target computer will be Site1. This is useful when you want to synchronize a website “as is” with a remote machine.
technology documents for car sales
An example that does not make sense:
msdeploy.exe -verb:sync -source:package=myapp.zip -dest:auto
Why have you ever set your destination to its original position? What's the point? Are you not just rewriting the source with iteslf?
The generated cmd file created when the package was published in VS2010 generates something like this:
"C:\Program Files\IIS\Microsoft Web Deploy V2\\msdeploy.exe" -source:package='MySourcePath' -dest:auto"
Does the auto automatically mean that the source will simply overwrite itself? But it’s not, it actually updates the IIS website (based on the settings in the manifest).
, , IIS.
, CI, msbuild/xcopy . msdeploy . , myproject.cmd, visual studio.
, SO dest.