Question about default logging on service crash about betterhostedservices HOT 2 OPEN

That's a good question. No I think it's honestly just a design oversight that I didn't log to an ILogger - probably because I wasn't sure if it would be flushed in time when the application exits less-than-gracefully. I'm still not sure it will for all implementations

If you want, I'd be happy to accept a PR that logs to both the ILogger and the Console interface.

from betterhostedservices.

I do think that you should use the built-in ILogger. By default, when you create a new project, this ILogger output to console, thus the user should still be able to see it if they look at the console output, or the docker output. Given that the .net host also use the ILogger abstraction to writer logs, I do think it's used by everyone.
Those like me that customized the ILogger to output elsewhere will also able to see those messages in their log file or in their remote logging service. I don't think there much of a user base for those that disable all logging of the microsoft ILogger and only output to console using a different logger.

I've created a pull request, feel free to edit it if you wish to have the console back.
#23

from betterhostedservices.