Cédric Luthi
Cédric Luthi
I just rebased my [ILoggerBuilder](https://github.com/0xced/testcontainers-dotnet/tree/ILoggerBuilder) branch on `develop` with all the builders and containers to not use `TestcontainersSettings.Logger` anymore.
@mdmathias @petea Any chance to get this merged?
Please go ahead! It's nice to see that there's now an active fork for BaGet. 😃
I think you might want to have a look at https://github.com/serilog/serilog/issues/1929 which is discussing a very similar issue.
I have now opened pull request #5180 to address this issue.
That's a good point. My claim about it being _impossible_ to do because the generated methods are private was wrong! I see two downsides to this approach, though. 1. You...
Cross-posting my comment from #1876 which can workaround this issue by defining the test logger parameters as MSBuild properties, where you have access to the target framework and the project...
I recently learnt that you can control the loggers through MSBuild properties instead of `dotnet test` arguments. Thus it becomes easy to craft the log file name of your choice....
I had the same issue (i.e. multiple `IHostedService` implementations running at build time) when I upgraded from `Microsoft.Extensions.ApiDescription.Server` version 6.0.10 to version 6.0.11. My workaround detects when the entry point...
Since it has both `api-approved` and `help wanted` tags I'd like to implement the MVC part. But before I dive into the implementation I'd like to be sure about the...