title: Issue manually deploying web package built in VSTS
body: <p>We have moved to VSTS in azure, with local builds.</p>
  
  <p>I have a asp.net mvc web application which I have create a build for which creates a web deploy package using the following parameters</p>
  
  <pre><code>/p:DeployOnBuild=true 
  /p:WebPublishMethod=Package 
  /p:PackageAsSingleFile=true 
  /p:SkipInvalidConfigurations=true  
  /p:AutoParameterizationWebConfigConnectionStrings=False
  </code></pre>
  
  <p>We then have releases which deploy to different environments e.g. DEV, QAL and TST. Works nicely all the parameters in the web.config are modified according to the parameters.xml file.</p>
  
  <p>Now comes the issue, we do not do automatic releases to production. So I take the web deploy package with the setparameters.xml file modified to meet the required configuration and other files and manually do in import into our IIS site. It completes but with these type of errors</p>
  
  <pre><code>25/08/2017 2:58:50 PM] Parameter entry 'wordAutomation_EndPoint/1' is applicable to 'C:\agent2\_work\6\s\Main\Clients\Web\WebUI\obj\Release\Package\PackageTmp\Web.config' because of its scope.
  [25/08/2017 2:58:50 PM] Parameter entry 'wordAutomation_EndPoint/1' could not be applied to 'C:\agent2\_work\6\s\Main\Clients\Web\WebUI\obj\Release\Package\PackageTmp\Web.config'. Deployment will continue with the original data. Details:
  No matches were found for the search string '/configuration/system.servicemodel/client/endpoint[@name='WordAutomationBasicHttpEndpoint']/@address' (type 'XmlFile').
  </code></pre>
  
  <p>So none of the parameters in the SetParameters.xml file are transformed into the web.config file.</p>
  
  <p>So currently I have a web deploy package which will deploy to IIS using the release task WinRM - IIS Web App Deployment, with no special parameters, but I cannot deploy the same package manually.</p>
  
  <p>Any ideas?</p>
  
  <p>Simon</p>