When using latest Quartz with System.Diagnostics.DiagnosticSource 7.0.0.0 or higher then jobs get stuck
See original GitHub issueWhen using Quartz.Net with System.Diagnostics.DiagnosticSource 7.0.0.X a job gets started but then gets stuck. When reverthing back to System.Diagnostics.DiagnosticSource 6.0.0.0 everything works as expected.
I also tried to add a binding redirect like this but that does not make any difference
<dependentAssembly>
<assemblyIdentity name="System.Diagnostics.DiagnosticSource" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-7.0.0.1" newVersion="7.0.0.1"/>
</dependentAssembly>
Issue Analytics
- State:
- Created 6 months ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Could not load file or assembly 'System.Diagnostics. ...
On installing latest version "5.0.1" of 'System.Diagnostics.DiagnosticSource' in NUget solved my issue. Hope it will fix yours also.
Read more >AspNet Net 6.0: FileLoadException: Could not load file or ...
1 with no Issues. 'System.Diagnostics.DiagnosticSource, Version=7.0.0.0' is resolved correctly by the PackageManager.
Read more >System.Diagnostics.DiagnosticSource 7.0.0-preview. ...
Provides Classes that allow you to decouple code logging rich (unserializable) diagnostics/telemetry (e.g. framework) from code that ...
Read more >DiagnosticSource and DiagnosticListener
This walkthrough shows how to create a DiagnosticSource event and instrument code with System.Diagnostics.DiagnosticSource. It then explains ...
Read more >.net azure function get user - Microsoft Q&A
Hi , i tried getting user from azure ad b2c through azure function in .net web api but i am getting the following...
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
It is on .net framework 4.8
Well I wanted to try to get you some logging but did see there was a new Diagnostic source version so I updated this to version 7.0.2 and now the problem is gone 😃 . I don’t know what has changed but I don’t have to problem anymore where to job just gets stuck.
Always nice those weird errors that solve themself.