Rolf Kristensen

I just tried to answer the question whether it only works as admin. I bet if you look in the MongoDb manual then you can find a much better answer...

Think it is a much better idea to make use of NLog Layout, and then just use `${configsetting}`. Then you can skip the dependency-hell. Example NLog.config: ```xml ``` Example appsettings.json:...

"Invalid Token" is returned from MongoDb. Do you have an NLog.config or other example of how you configure the NLog Target? Have you checked the [NLog InternalLogger](https://github.com/NLog/NLog/wiki/Internal-Logging) for clues?

Googled it for you, and this came up: https://stackoverflow.com/questions/5334661/system-badimageformatexception-invalid-token-when-updating-dll-to-newest-versi

Maybe you can try this pre-release-nuget-package (From PR #41) and report the output from NLog InternalLogger (At Debug-Level): https://ci.appveyor.com/project/LoreSoft/nlog-mongo/builds/33782375/artifacts

There is now an updated nuget-package, that should improve the speed: https://www.nuget.org/packages/NLog.Mongo/

Notice `${exception:format=tostring}` and `${message:withexception=true}` both outputs the result of `Excetion.ToString()` But `Excetion.ToString()` only provide line-numbers and source-code-filenames when PDB-/symbol-files are available in the deployment folder.

Still `up-for-grabs` and there has been no takers, so free for the taking. Or open for discussion if this proposal is stupid.

Think a spike might need to be made for NET35 to ensure we depend on a compiler-feature and not a runtime feature (like caller-member-attributes). Else we need to wait for...

Maybe the `System.Text.Json` is not a good choice for handling random objects, since it seems very fragile. Maybe `MetaDataDictionaryConverter` should only support simple-types (bool, int, DateTime, etc.), and perform `ToString`...