You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-15Lines changed: 0 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -115,21 +115,6 @@ For legacy .NET Framework projects it also scans default probing path(s).
115
115
116
116
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.
117
117
118
-
#### .NET Single File Applications
119
-
120
-
Currently, auto-discovery of configuration assemblies requires special care when the application is deployed in [bundled mode](https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file/overview).
121
-
122
-
Starting with version 3.4.0, the configuration assemblies must be explicitly loaded prior to calling `loggerConfiguration.ReadFrom.Configuration(…)`.
123
-
124
-
```csharp
125
-
// Force loading of assemblies that might be used in the configuration (required when published as single file)
For versions older than 3.4.0, the [Using](#using-section-and-auto-discovery-of-configuration-assemblies) section must be used to load configuration assemblies as a workaround.
132
-
133
118
### MinimumLevel, LevelSwitches, overrides and dynamic reload
134
119
135
120
The `MinimumLevel` configuration property can be set to a single value as in the sample above, or, levels can be overridden per logging source.
0 commit comments