How do you use IPdfPageCollection in C# code?

Accept IPdfPageCollection as a parameter or return type in C# code that needs to work uniformly across IronPDF implementors. The interface defines the contract; concrete behavior is provided by the implementor returned at runtime.

What is the difference between IPdfPageCollection and a concrete implementor?

IPdfPageCollection is the interface contract; its concrete implementors carry the actual behavior. Reference IPdfPageCollection when writing code that should work across multiple implementors; use a concrete type when a single implementor's behavior is required.

Which namespace and assembly contain IPdfPageCollection?

IPdfPageCollection is in the IronPdf.Pages namespace, shipped in IronPdf.dll. It extends IDocumentPageCollection . Concrete classes such as PdfPagesCollection implement it.

Interface IPdfPageCollection

Q: What implements IPdfPageCollection in IronPDF?

Concrete implementors of IPdfPageCollection in IronPDF include PdfPagesCollection. Code that accepts IPdfPageCollection works uniformly across all implementors, with a cast to the concrete type only required when type-specific behavior is needed.

Collection of PDF pages

Namespace: IronPdf.Pages

Assembly: IronPdf.dll

Syntax

public interface IPdfPageCollection

IPdfPageCollection is the contract IronPDF C# code works through for PDF pages. It represents collection of PDF pages, so code can work with PDF pages uniformly across implementors rather than binding to a concrete type.

Concrete implementors include PdfPagesCollection, IronPDF concrete implementor. Code that accepts IPdfPageCollection works uniformly across these implementors, so applications can read or configure C# PDF features without binding to a specific concrete type.

Most of the usable surface is inherited. The members that carry everyday use of this contract are the IPdfPageCollection contract members, the IPdfPageCollection contract members; consult these first when implementing or consuming IPdfPageCollection. The add copy delete pages PDF walks through typical use in the IronPDF C# documentation.

using IronPdf;

// IPdfPageCollection is consumed as the API surface for the family of implementors
void Consume(IPdfPageCollection target)
{
    // Use members defined on the interface; concrete behavior follows the implementor
}

For collection-wide operations and end-to-end examples, see the IronPDF C# documentation for related guides. For collection-wide operations on IPdfPageCollection instances, the IronPDF C# documentation lists the relevant container types and their methods. Concrete behavior depends on which implementor of IPdfPageCollection is returned at runtime; consult the specific class reference for type-specific members. Polymorphic access through IPdfPageCollection lets code work uniformly across the family of implementors, with a cast required only when type-specific behavior is needed. The reference tables below list the full set of members defined on IPdfPageCollection along with any inherited members exposed through the contract. In a typical IronPDF C# workflow, IPdfPageCollection appears as a parameter or return type at the boundary between the application and the IronPDF API. See the methods table below for the complete set of members defined directly on IPdfPageCollection. Implementing IPdfPageCollection directly in application code is uncommon; the typical pattern is to consume instances returned from the IronPDF API.