.NET Core Linux not logging Entity Framework Core transactions
See original GitHub issueI published my app using:
dotnet publish -r linux-x64 -f netcoreapp2.2 --self-contained -c Release
The app works, requests end up in APM server, but no entity framework transactions. Running the app from Rider on Windows works just fine. Is this a known thing with self-contained releases?
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Logging in .NET Core and ASP.NET Core
Learn how to use the logging framework provided by the Microsoft.Extensions.Logging NuGet package.
Read more >Alternative to TransactionScope (DTC) for .NET Core ...
I am currently working on a project where my program runs in a Linux Docker container and my database is hosted on a...
Read more >Entity Framework Core - Use TransactionScope With ...
NET Core and knows Entity Framework inside out. One of the new features of Entity Framework Core 2.1 is the support of TransactionScopes....
Read more >Logging in Entity Framework Core
Entity Framework Core integrates with the .NET Core logging to log SQL and change tracking information to the various output targets. First, install...
Read more >Transactions with Entity Framework Core
I explained how to create a model from a database and call stored procedures. Here I explain transactions with Entity Framework Core.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m working on a repro project, but cannot really find anything yet. Next week, I’ll try to work on trimming down my product to a version that’s OK to share, and still shows the issue…
Ok, closing now, feel free to reopen when you have time for this.