API Reference
PdfSerializationReport
Runtime evidence describing how one PDF save bounded completed payloads.
Inheritance
- Object
- PdfSerializationReport
Usage
This type appears in these public API surfaces even when no hand-authored example is attached directly to the page.
Returned or exposed by
- Property PdfSaveResult.Serialization
Inherited Methods
Properties
public Nullable<Int32> PageCount { get; } #Generated or inspected page count when known.
public Int64 BytesWritten { get; } #Complete PDF bytes written to the destination.
public Int64 PageContentMemoryLimitBytes { get; } #Configured completed-page-content memory limit.
public Int64 ObjectBufferMemoryLimitBytes { get; } #Configured per-store completed-object memory limit.
public Int64 PeakRetainedPageContentBytes { get; } #Highest completed page-content byte count retained by the bounded store.
public Int64 PeakRetainedObjectBytes { get; } #Highest combined completed indirect-object byte count retained by simultaneously live assembly stores.
public Boolean PageContentSpilled { get; } #True when completed page/effect content spilled to temporary storage.
public Boolean ObjectBufferSpilled { get; } #True when completed indirect objects spilled to temporary storage.
public Boolean FinalArtifactBuffered { get; } #True when the final artifact was intentionally materialized as a byte array.
public Boolean SourcePassthrough { get; } #True when an opened artifact was copied without generated layout or object assembly.
public Boolean IsForwardOnlyLayout { get; } #False until layout, replay, and deterministic object allocation support genuinely forward-only output.
public Boolean UsesBoundedCompletedPayloadStores { get; } #True when generated completed payloads were governed by explicit memory limits.