README and sample updates for v3.0

[nblumhardt]

Once v3.0 of this project ships, we should show use of IHostBuilder through Serilog.Extensions.Hosting instead of the IWebHostBuilder code we continue to support here for backward compatibility. There are also some new features to document.

• Update the README and samples here to use IHostBuilder and current ASP.NET Core conventions
• Update the Serilog.Extensions.Hosting README to replicate the more detailed information about early vs. inline initialization, and provider support, currently documented in this project
• Add documentation for IDiagnosticContext
• Include Debug, Console, and File sinks as dependencies, with example usage in the README; Settings.Configuration may also be worth consideration

[carlowahlstedt]

Not sure if this is for compatibility with Core 3, but enabling Serilog is eating the output to the debug console after upgrading. Here's my Program.cs post upgrade where I had to comment out Serilog to get the output to the debug console to work.

I couldn't find any other way to enable Serilog with the extension method, docs, or anything else that gave be an idea of what I might be doing wrong.

[nblumhardt]

Thanks for the heads-up. You need WriteTo.Debug() in your Serilog configuration if you want log events to go to the debug console (dotnet add package Serilog.Sinks.Debug) - it wouldn't hurt if we take a dependency on this and the console sink from this package, I'll make that change and include this info in the README. Cheers!

[carlowahlstedt]

Thanks for the quick response. I only noticed because opening of the browser window in vs code stopped working after the update. Finally tracked it back to that.

[rogerfar]

Is there an upgrade path needed from 2.x to 3.0? It looks like the CHANGES.MD isn't kept up to date.

[nblumhardt]

Hi @rogerfar - thanks for pointing out the unmaintained CHANGES.md. I've just deleted it - changes are now tracked per release in https://github.com/serilog/serilog-aspnetcore/releases

There are no API-breaking changes in v3.0, though some functionality has moved around between packages under the hood.

If you encounter any issues upgrading, let us know, we'll pop some notes into the 3.0.0 milestone release notes. Thanks!

[nblumhardt]

#111 is tracking the last of the example changes.