k web and k kestrel should give the url/port on the command line about hosting HOT 8 CLOSED

RE: aspnet/HttpSysServer#74 (private).

It doesn't print this today because Hosting doesn't know, only WebListener/Kestrel knows, and WebListener shouldn't be doing random Console.WriteLine's.

from hosting.

What about the commands themselves? Can the printout they printout the arguments?

from hosting.

While I agree that WebListener/Kestrel shouldn't be doing random Console.Writelines. There should be a consensus on at the very least logging this information. At which point it would be useful to simply redirect the logging to standard output or wherever else we wish to choose. Right now the current setup is very inflexible and doesn't give you much verbosity in terms of logging information.

from hosting.

That is the current proposal: The servers should "...log the addresses at startup as Informational, and the console logger will display it by default."

from hosting.

It doesn't look like this is getting any attention.

@glennc should I close this item?

from hosting.

It's happening, we just needed to do some work on the console logger first to make the output legible. aspnet/Logging#70

from hosting.

This has been done, you can see the url and port if you have a console logger attached, which the default template does.

from hosting.

Can someone explain why everything with Microsoft has to be so complicated. Why not just add a flag to see directly the console output or someone could just post a full description instead of cryptic answers. Lot's of people have issue and there is barely documentation available and people land here and find an uncompleted answer. You can't expect that everyone is involved in the core development of ASP.NET 5.0. Although promising it has been more than frustrating so far.

from hosting.