title: Azure Web Deploy "Publish Failed"
body: <p>Hello my fellow developers!</p>
  
  <p>I am currently struggling with a problem in the latest Visual Studio 2017 Professional - Version 15.8(.1).</p>
  
  <p>Since The Update to Version 15.8, I am unable to publish any Azure Function via Web Deploy.</p>
  
  <p>Every time i press the "Publish" button, I simply get an error window saying: "Publish failed". The Output window stays empty, where normally I would get all the build and publishing output.</p>
  
  <p><strong>What I've tired:</strong></p>
  
  <ul>
  <li>Cleaned the solution; deleted %temp%; deleted the publishing profile; reset the publish credentials in Azure; build it all again and import a newly generated publish profile: Same Error</li>
  <li>Uninstalled VS2017; Cleaned all remains; Reinstalled VS2017: Same Error</li>
  <li>Checked our Firewall, if anything gets blocked and even tried an exception for my workstation to allow all traffic: Same Error</li>
  <li>Tried publishing from a physically different Network: Same Error</li>
  <li>Stop the Function in the azure portal prior to publishing: Same Error</li>
  <li>In the azure portal: Delete an create a new and empty azure function to publish to: Same Error</li>
  <li>In the azure portal: Set the 'Function app edit mode' to Read/Write: Same Error</li>
  <li>Tried to hit the functions Endpoint-URL in the browser. No Problem.</li>
  <li>Tried to publish from a colleagues workstation with Visual Studio 2017 Pro Version 15.7.1: <strong>Works fine - as used to</strong></li>
  </ul>
  
  <p><strong>My Questions:</strong></p>
  
  <ul>
  <li>Am I missing something? Is there anything else I can try except installing an older version of Visual Studio, which would be my next step.</li>
  <li>Could this be a bug in the latest Azure Tools or even Visual Studio?</li>
  <li>Why is my Output window not giving me any information to address the failing publishing attempt? Am I missing some new option to activate this again?</li>
  </ul>
  
  <p>I hope someone can point me in the right direction to solve this infuriating issue ;)</p>