Updated Settings (markdown)

Stef Heyenrath
2019-01-06 11:21:53 +01:00
parent 1c5cf336b2
commit 088e7e4c3b

@@ -75,13 +75,18 @@ Action which is called (with the IAppBuilder or IApplicationBuilder) after the i
The [IWireMockLogger](https://github.com/WireMock-Net/WireMock.Net/blob/master/src/WireMock.Net/Logging/IWireMockLogger.cs) interface which logs Debug, Info, Warning or Error.
By default this is implemented by a default console logger [WireMockConsoleLogger.cs](https://github.com/WireMock-Net/WireMock.Net/blob/master/src/WireMock.Net/Logging/WireMockConsoleLogger.cs).
But also a Null logger is available [WireMockNullLogger.cs](https://github.com/WireMock-Net/WireMock.Net/blob/master/src/WireMock.Net/Logging/WireMockNullLogger.cs).
/// <summary>
/// Handler to interact with the file system to read and write static mapping files.
/// </summary>
[PublicAPI]
IFileSystemHandler FileSystemHandler { get; set; }
And you can implement your own logger, like [WireMockLog4NetLogger.cs](https://github.com/WireMock-Net/WireMock.Net/blob/master/examples/WireMock.Net.Service/WireMockLog4NetLogger.cs).
### FileSystemHandler
Handler to interact with the file system to read and write static mapping files.
By default this is implemented by the [LocalFileSystemHandler.cs](https://github.com/WireMock-Net/WireMock.Net/blob/master/src/WireMock.Net/Handlers/LocalFileSystemHandler.cs), however you can implement your own version as defined here as an example [CustomFileSystemFileHandler.cs](https://github.com/WireMock-Net/WireMock.Net/blob/master/examples/WireMock.Net.Console.Net452.Classic/CustomFileSystemFileHandler.cs).
Implementing your own version from this FileSystemHandler can be useful when running in Azure or Docker Containers.