Sergey Komisarchik

@rodrigoramirez93 Hi, can you provide minimal example that reproduces the problem? Thanks!

Hi @aiampogi , @rodrigoramirez93 looks like a problem with [dotnet publish](https://github.com/serilog/serilog-settings-configuration/issues/288#issuecomment-974802456) on `sln` which can have unpredicted side effects.

Hi @ranasch @hunyhabib try [this](https://github.com/serilog/serilog-settings-configuration/pull/222#issuecomment-919916935) workaround

Looks similar to [this](https://github.com/serilog/serilog-settings-configuration/issues/196) issue. @rati-openkey try to install latest `Serilog.Settings.Configuration` version and see if it helps

@nblumhardt out-of-band package with extension methods would be good option and for the abstractions like MEL. Unfortunately, overload resolution prefer signature with string interpolation handler only if method defined on...

Hi, @augustoproiete. I believe its by design. 'SourceContext' is valid in `ForContext` context, otherwise its just a regular property. `ForContext(..)` will create static pipeline with minimum level applied upfront for...

One way could be is to capture exception with `ExceptionDispatchInfo.Capture(..)` in the core, pass it along with the `LogEvent` object to downstream sink, rethrow it (optionally) there, and emit with...

Mimicking original exception with the subclassed one (`ExceptionInfo`) still could create behavior change in downstream sinks when `is` operator won't work as before along with the `GetType()` and other non-virtual...

The runtime support is coming to `.net core 2.1` (https://github.com/dotnet/coreclr/pull/16464) (and eventually to the full framework I believe). No need to use `ExceptionDispatchInfo`. For the [#521](https://github.com/serilog/serilog/issues/521) there is also [improvement](https://www.ageofascent.com/2018/01/26/stack-trace-for-exceptions-in-dotnet-core-2.1/)...

Hi @kentonbmax , To be able to use `Microsoft.Extensions.Logging` filters you need to put `Serilog` sub-section: ```json "Logging": { "Serilog": { "LogLevel": { "Default": "Warning", ... } } ``` and...