skip static constructor on binding for complex parameters types

Author: Sergey Komisarchik

CHANGES.md

@@ -12,6 +12,7 @@
 * #231 - make '$' sign optional for minimum level / filter switch declarations
 * #237 - DependencyContextAssemblyFinder fix: check `serilog` at the start of the name for any dependent package
 * #239 - handle NotSupportedException for .net 5.0 single file applications
+* #260 - skip static constructor on binding for complex parameters types
 
 3.1.0
 

README.md

@@ -35,7 +35,7 @@ static void Main(string[] args)
     var configuration = new ConfigurationBuilder()
         .SetBasePath(Directory.GetCurrentDirectory())
         .AddJsonFile("appsettings.json")
-        .AddJsonFile($"appsettings.{Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT")}.json", true)
+        .AddJsonFile($"appsettings.{Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT") ?? "Production"}.json", true)
         .Build();
 
     var logger = new LoggerConfiguration()
@@ -74,6 +74,13 @@ var logger = new LoggerConfiguration()
 
 `Using` section contains list of **assemblies** in wich configuration methods (`WriteTo.File()`, `Enrich.WithThreadId()`) resides.
 
+```json
+"Serilog": {
+    "Using":  [ "Serilog.Sinks.Console", "Serilog.Enrichers.Thread", /* ... */ ],
+    // ...
+}
+```
+
 For .NET Core projects build tools produce `.deps.json` files and this package implements a convention using `Microsoft.Extensions.DependencyModel` to find any package among dependencies with `Serilog` anywhere in the name and pulls configuration methods from it, so the `Using` section in example above can be ommitted:
 
 ```json
@@ -106,11 +113,11 @@ var logger = new LoggerConfiguration()
 
 For legacy .NET Framework projects it also scans default probing path(s).
 
-For all other cases, as well as in the case of non-conventional configuration assembly names **DO** use `Using` section.
+For all other cases, as well as in the case of non-conventional configuration assembly names **DO** use [Using](#using-section-and-auto-discovery-of-configuration-assemblies) section.
 
 #### .NET 5.0 Single File Applications
 
-Currently, auto-discovery of configuration assemblies is not supported in bundled mode. Use `Using` section for workaround.
+Currently, auto-discovery of configuration assemblies is not supported in bundled mode. **DO** use [Using](#using-section-and-auto-discovery-of-configuration-assemblies) section for workaround.
 
 ### MinimumLevel, LevelSwitches, overrides and dynamic reload
 

src/Serilog.Settings.Configuration/Settings/Configuration/StringArgumentValue.cs

@@ -104,7 +104,7 @@ public object ConvertTo(Type toType, ResolutionContext resolutionContext)
                     throw new InvalidOperationException($"Type {argumentValue} was not found.");
                 }
 
-                var ctor = type.GetTypeInfo().DeclaredConstructors.FirstOrDefault(ci =>
+                var ctor = type.GetTypeInfo().DeclaredConstructors.Where(ci => !ci.IsStatic).FirstOrDefault(ci =>
                 {
                     var parameters = ci.GetParameters();
                     return parameters.Length == 0 || parameters.All(pi => pi.HasDefaultValue);

test/TestDummies/DummyThreadIdEnricher.cs

@@ -5,6 +5,10 @@ namespace TestDummies
 {
     public class DummyThreadIdEnricher : ILogEventEnricher
     {
+        static DummyThreadIdEnricher()
+        {
+        }
+
         public void Enrich(LogEvent logEvent, ILogEventPropertyFactory propertyFactory)
         {
             logEvent.AddPropertyIfAbsent(propertyFactory