Skip to content
This repository has been archived by the owner on Dec 19, 2018. It is now read-only.

k web and k kestrel should give the url/port on the command line #89

Closed
sayedihashimi opened this issue Oct 9, 2014 · 8 comments
Closed

Comments

@sayedihashimi
Copy link

Today when k web or k kestrel are invoked the default output is simply Started. It would be much better to include the url/port which was just started. W/o this users will need to look into project.json to figure out the port number.

@Tratcher
Copy link
Member

Tratcher commented Oct 9, 2014

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.

@sayedihashimi
Copy link
Author

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

@nyxtom
Copy link

nyxtom commented Nov 13, 2014

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.

@Tratcher
Copy link
Member

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

@sayedihashimi
Copy link
Author

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

@glennc should I close this item?

@Tratcher
Copy link
Member

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

@glennc
Copy link
Member

glennc commented Feb 12, 2015

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

@glennc glennc closed this as completed Feb 12, 2015
@flyandi
Copy link

flyandi commented Jul 13, 2015

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants