This version of TracerX-Logger.dll REMOVES support for Logger.InfoCall(), Logger.DebugCall(), etc. in methods that use async/await. An exception or very weird behavior will occur if you use the await keyword inside a "using (Logger.InfoCall())" block. Otherwise, this feature still works.
For documentation see the TracerX article on CodeProject (https://www.codeproject.com/Articles/23424/TracerX-Logger-and-Viewer-for-NET).
To use the logger in your application, install the TracerX-Logger NuGet package.
TracerX-Viewer_9.1.zip - Run TracerX-Viewer.exe to enumerate and view TracerX logs on your local computer. It can also connect to TracerX-Service.exe running on remote computers to view remote log files without using shares.
Sample_9.1.zip - If you run Sample.exe it generates a log file you can view with TracerX-Viewer.exe. Try the Logger and ThreadName filters in the viewer.
TracerX-Service_8.0.zip - This optional component enables remote viewing of log files without using shares or remote desktop. It's basically a file server for TracerX log files. When TracerX-Service.exe is running the TracerX-Viewer app can connect from remote computers to enumerate and view available logs. TracerX-Service.exe can be run as a service or a console app (e.g. for testing). Run it with the "-h" switch for help on how to run it as a console app or self-install (and uninstall) the service.
You can convert your own service or application to a TracerX log server by referencing TracerX-ServiceImpl.dll and calling it's TracerXServices.Startup() method. That's basically what TracerX-Service.exe does. Also, the viewer does that if you click on the File menu and select the "Run TracerX Service" option.