Note: This API is now obsolete.

[ObsoleteAttribute("Use Fix property")]
public void FixVolatileData(
	bool fastButLoose
)

<ObsoleteAttribute("Use Fix property")>
Public Sub FixVolatileData ( 
	fastButLoose As Boolean
)

public:
[ObsoleteAttribute(L"Use Fix property")]
void FixVolatileData(
	bool fastButLoose
)

[<ObsoleteAttribute("Use Fix property")>]
member FixVolatileData : 
        fastButLoose : bool -> unit 

Parameters

fastButLoose

Type: SystemBoolean
Set to true to not fix data that takes a long time to fix.

Some of the values in instances of LoggingEvent are considered volatile, that is the values are correct at the time the event is delivered to appenders, but will not be consistent at any time afterwards. If an event is to be stored and then processed at a later time these volatile values must be fixed by calling [M:FixVolatileData()]. There is a performance penalty for incurred by calling [M:FixVolatileData()] but it is essential to maintaining data consistency.

The fastButLoose param controls the data that is fixed. Some of the data that can be fixed takes a long time to generate, therefore if you do not require those settings to be fixed they can be ignored by setting the fastButLoose param to true. This setting will ignore the LocationInformation and UserName settings.

Set fastButLoose to false to ensure that all settings are fixed.

Reference