IpcServiceFramework VS Audit.NET

The accepted answer states the you could use named pipes, but at the time we could not create a reliable communication between unity and WPF, because named pipes would randomly drop with unity. We ended up using this https://github.com/jacqueskang/IpcServiceFramework with TCP. Both unity and the WPF app had a server and a client so we could do two-way communication. (Altough you can use a number of other solutions for this. Maybe create a file which holds messages, one process reads it and the other writes to it)

I’ve had great success using Audit.Net. It supports a variety of different data stores and I believe it logs things in a background thread…I could be wrong though. At any rate, I have been using it with the EF provider and a custom table. No issues thus far.

I've looked into this as well and kept seeing https://github.com/thepirat000/Audit.NET pop up. There's also this huge thing https://abp.io/ that has auditing as a component.

Sounds like you could use Audit.NET

Next, I started looking into different available options. I came across various libraries, compare them and finally I chose Audit.Net WebApi for the following reasons:

There are about a billion packages for accomplishing this, e.g. https://github.com/thepirat000/Audit.NET/tree/master/src/Audit.EntityFramework - for everyone reading this, please use tried-and-tested packages like that, instead of this yet-another-reinvention-of-the-wheel.