I am trying to publish some internal use only asp.net projects to a server on our lan. There are several aspects of this that I'm confused about.
Using vs 2017, webdeploy successfully published the site. However when I try to access the site, I get a 404 error. I get this error regardless of whether I spec the ip address of the server, and/or the default.aspx page, or index.html which I manually created
for testing purposes after this issue arose.
What is particularly noteworthy is that while the project has been published to c:\inetpub\box on the server (2012 r2), the 404 error lists the physical path as c:\inetpub\wwwroot\box, which does not exist.
I suspect that the issue may be that I misunderstand how to configure what I'll call a "subsite". I would like several asp.net projects to be published on this server, at addresses like
http://myserver/box
http://myserver/contact
the root website, http://myserver, might just contain a page with links to the subsites.
I can reach http://myserver and it shows the default.aspx that I have in wwwroot, which is a good indication that wwwroot is regarded as the go-to site for iis.
In IIS I created the new website box and the physical path there is listed as c:\inetpub\box
There are other websites on the same server from earlier tests. All of them run on port 80.
The 404 error message shows off the incorrect physical path c:\inetpub\wwwroot\box, it seems that wwwroot somehow has precedence and gets injected into url request like http://myserver/box. How do I adjust this?