LogFactory - Avoid checking candidate NLog-config files for every Logger created

[snakefoot]

NLog should not introduce a performance-hit during application-startup when not able to load NLog.config (Or no NLog.config available). The performance-hit would depend on the number of unique Logger-objects that are created.

Before it would attempt to scan all NLog-config-candidate-file-locations for every unique Logger-object created by the application (until NLog-config has been loaded). Now it will only do an initial auto-scan on the first Logger-creation.

One could consider creating a fluent Setup()-extension-method that starts file-watchers for all candidate-locations, that stays active until a valid NLog-configuration is loaded. See also #1114

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication