How do you use IPdfImageObjectCollection in C# code?

Accept IPdfImageObjectCollection 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 IPdfImageObjectCollection and a concrete implementor?

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

What namespace is IPdfImageObjectCollection defined in?

IPdfImageObjectCollection is in the IronSoftware namespace, shipped in IronPdf.dll. It extends IDocumentImageObjectCollection . Concrete classes such as ImageObjectCollection implement it.

Interface IPdfImageObjectCollection

Q: What implements IPdfImageObjectCollection in IronPDF?

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

Collection of PDF image objects

Namespace: IronSoftware

Assembly: IronPdf.dll

Syntax

public interface IPdfImageObjectCollection

Working with Iron Software API through a shared contract runs through IPdfImageObjectCollection. It represents collection of PDF image objects, so code can work with Iron Software API uniformly across implementors rather than binding to a concrete type.

Concrete implementors include ImageObjectCollection, IronPDF concrete implementor. Code that accepts IPdfImageObjectCollection 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 IPdfImageObjectCollection contract members, the IPdfImageObjectCollection contract members; consult these first when implementing or consuming IPdfImageObjectCollection. The image to PDF walks through typical use in the IronPDF C# documentation.

using IronPdf;

// IPdfImageObjectCollection is consumed as the API surface for the family of implementors
void Consume(IPdfImageObjectCollection 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 IPdfImageObjectCollection instances, the IronPDF C# documentation lists the relevant container types and their methods. Concrete behavior depends on which implementor of IPdfImageObjectCollection is returned at runtime; consult the specific class reference for type-specific members. Polymorphic access through IPdfImageObjectCollection 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 IPdfImageObjectCollection along with any inherited members exposed through the contract. In a typical IronPDF C# workflow, IPdfImageObjectCollection 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 IPdfImageObjectCollection. Implementing IPdfImageObjectCollection directly in application code is uncommon; the typical pattern is to consume instances returned from the IronPDF API.