The issue appears to be with VS 2017 itself, it’s not setting the url properly from the publish settings, and tries to publish to the server root giving 401 unauthorised. If you modify the server url for publishing to have the IIS site name e.g. https://Server_name:8172/msdeploy.axd?site=IISAppname it will publish.
Funny that I saw you post as soon as I came to the forum to mention it with VS 2015.
With 2015 it only seems to work for me with the straight server name “server.com” and no pre “http://” and no trailing “msdeploy.axd” in the VS Server setting in the publishing settings.
I did have a client mention it wasn’t working with 2017 so will try your suggestion.
I think this needs to be tested across versions and some code added to accommodate the publishing file generation and download based on the clients choice of version to download the file for. Maybe a drop down or radio option on the publishing file download screen.
What do you think?
- Views5717 times
- Answers3 answers