-
Notifications
You must be signed in to change notification settings - Fork 58
Creating .NET Core web app that includes 'web' or 'app' in the name silently fails to launch in VS (it just hangs on launch) #176
Comments
From @benaadams on May 10, 2016 23:54 The error means the port Kestrel is trying to listen on already has something listening on it |
From @halter73 on May 11, 2016 0:3 @benaadams Agreed that that is the most likely explanation. @CesarBS Said he was able to repro and that he would debug it. |
From @CesarBS on May 11, 2016 0:47 @benaadams I'm not sure. When you try to listen on a port that's already in use you normally get an |
Specifically, the ASPNETCORE_APPL_PATH is set to |
@pan-wang Is |
Facing same problem when project name includes "Web", in my case project name is Transfer.Web |
I have a Project.WebSite and it works fine. Can be repro only when it ends with Web? |
Renamed my project to |
It does seem to be related to ANCM or Kestrel. I can create and run an MVC5\Webform application with the name web. |
I don't think Web is a reserved keyword in either IIS and IISExpress. Will look at it. |
Can confirm creating a new project in RC2 (net461) and naming it Web causes this in VS. Was not the case in RC1. This happen in both brand new projects and those converted from RC1. |
this is bug in ANCM. When resolving the site path, it simply takes the sub string from the app path using the site name and did not consider the app path may already contains string as 'WebRoot' and "AppHost". Will fix it. |
Root cause: ANCM had a bad IndexOf on the string |
My project was named |
As you see in #193 it also fails when the url is something like "http://app.whatever.tld/SaveProjectNameHere" |
@road42 That was because you set your root site name to |
@Tratcher Ah sorry this wasn't clear enough. Thank you. |
I've just come across this issue when deploying an update to a site running RC2 (which was already RC2) when accessing it at |
@martincostello I don't think so, it has worked for others on azurewebsites.net. |
@Tratcher I've been playing around with this, and I think I've actually narrowed it down to there being RC1 and RC2 bits in the same wwwroot folder after the "delete existing files" option wasn't used when publishing the site. However, I've no idea what change triggered it suddenly making a difference. Deleting every file in wwwroot in Azure, re-publishing and restarting the site fixed the problem with the site not starting. |
I migrate a solution from RC1 to RC2 and one of the projects was named "Web". I rename it (both name and folder) but I'm still get the same error. Are there "strange" steps to rename a projects? |
@cherici-simone what was the new name? |
@cherici-simone was the error on IIS, Express, or Azure? In Express the project name is used. In IIS and Azure it's the site name. |
I try "Site" but nothing...then I try..."aaa" but the error persist. I try On Wed, Jun 15, 2016 at 5:50 PM, Murat Girgin [email protected]
Simone Cherici |
@cherici-simone Is this in Azure? I had issues with a RC1 -> RC2 migration in Azure because there were things left in the site folder for RC1 that created strange conflicting behaviour. Deleting the RC1 remnants via FTP fixed it. |
In my case, changing the port I was using fixed it.. maybe that port was already busy |
Cleans up IIS initialization testing framework
Thanks for the comments. |
From @BillHiebert on May 10, 2016 23:51
Create a new Empty .NET Core Web app in VS
Call it "web"
Hit F5 (to launch under IIS Express)
Actual:
It fails to launch (spinning Edge icon waiting for it to load) - there are not even an IIS Express logs to debug the issue
What's happening is kestrel is throwing the following exception. It only repros with projects named "web" and when hosted in iisexpress.
Copied from original issue: aspnet/KestrelHttpServer#824
The text was updated successfully, but these errors were encountered: