I have a website that I would like to publish on a local server. I find this simple task quite difficult.
My problems start with the Web Deploy (1.1) tool giving me 401 Unauthorized as an administrator because port: 8172 appears in errors and this port is blocked, but the documentation says: "By default, ListenURL is http: // +: 80 / MsDeployAgentService "!
I do not like to open another port, and these days I have little patience, so I thought that it will be created, I will create a Web Deploy package and import it into IIS on the server through RDP.
First of all, I noticed that Visual Studio does not use the dialog box to collect the settings or uses my publishing profiles, but it seems to use the tab in the project properties, although I think they are ignored when importing the package anyway?
Now I am sitting in the import wizard using the application path and connection string. I cleared the conn line, because I think it’s for some ASP files that I don’t use, but when I don’t enter anything in the Application Path, the wizard barks at me, saying that I'm mostly weird because most people publish to folders under the root site.
Now I want my site to be site.com/Home/About, not site.com/subfolder/Home/About, and I think this is an MVC redirect site that subfolder introduces other headaches. Should I go ahead and use the root?
Finally, I also want to publish a web service at www.site.com/services/soap, which I think can handle IIS.
By typing this question, Amazon provided my IIS 7 resource set, and I was scouring the Internet, but actually I am becoming more confused.
The comment here seems to show a consensus view that Publish is not for production sites, and that real men are rolling their own.
ASP.NET Publish Website Compared to Web Deployment Project
... I assume this was the era of web deployment?
Now I am going to experiment on a spare box, but any help is appreciated.
Luke
UPDATE
( ) Web Deploy, . " " system.web.extensions/scripting/scriptResourceHandler ", 4.0 2.0.