aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
258 stars 124 forks source link

web deploy on windows 10 #1085

Open vikasNew opened 5 years ago

vikasNew commented 5 years ago

Hello,

can i publish my code by using web deploy to windows 10 machine.

i have setup my testing windows 10 machine for deployment, which is in local area network.

So i want to publish my code to that remote machine by using web deploy. can i do that ?

i have installed web deploy and also enabled web development remote service on windows 10 but i am not able to connect to remote machine using we deploy.

This returns me the following error every-time. "ERROR_DESTINATION_NOT_REACHABLE"

interesting thing is i also have windows 10 on my machine & i am able to use web deploy on my local machine but it's not working with remote windows 10 machine.

is web deploy only meant for Windows servers not for other normal windows?

Thanks

barrytang commented 5 years ago

@shirhatti

shirhatti commented 5 years ago

Sounds like wmsvc is not listening on the destination machine. Try following the instructions at https://docs.microsoft.com/en-us/iis/manage/remote-administration/remote-administration-for-iis-manager

shirhatti commented 5 years ago

is web deploy only meant for Windows servers not for other normal windows?

Not the case

vikasNew commented 5 years ago

Hi

Thanks for the Reply,

WMSVC(Web Management Service) is already running on remote system. i have confirmed this from services.

still not working for me....My Target Remote machine has windows 10 installed instead of any windows server

Any other suggestions..?

Thanks in anticipation

stact commented 4 years ago

Seems to be a bug. Got the same error. All is well configured.

Don't use the Azure "Azure Virtual Machines" publisher Configure IIS, FTP, etc instead image

For "server" use http:// image

Working from my side, any other configuration shared by Web Deploy configuration.

Please Core Team: fix this unexpected behavior, let Azure VM works and allow servername on configuration for the server instead http:// :)

Hope it helps!