Control over registry operations in Windows and .NET applications

CallbackRegistry.FlushFilesOnOpen property


Pascal    C++ (Lib)    C++ (VCL)    C++ (.NET)    C#    VB.NET   



Specifies whether unused orphan memory mappings should be closed when the file is opened.


    property FlushFilesOnOpen : boolean;

[C++ (Lib)]
    void SetFlushFilesOnOpen(BOOL Value);
    bool GetFlushFilesOnOpen(void);

[C++ (VCL)]
    __property bool FlushFilesOnOpen;

[C++ (.NET)]
    property bool FlushFilesOnOpen

    bool FlushFilesOnOpen;

    Public Property FlushFilesOnOpen As Boolean


Sometimes after the file is closed, an open memory mapping (MMF) still exists. When the file is opened the next time by the application, the data is taken from the MMF rather than from the disk. This is not a problem when your application doesn't change the data being read (eg. decrypts them). However, if the data read from the disk are decrypted, decrypting the data that comes from the MMF (which is not encrypted) would produce garbage on output. To address this problem you need to set this property to true, and the driver will check presense of MMF and close it before opening the file. This will ensure, that the data is read from the disk.

Default value is false to speed up file opening.

Property value can be changed only when when the filter is active, i.e. Active is true.

Back to top