How do you use IPdfPathObjectCollection in C# code?

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

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

Where is IPdfPathObjectCollection located in the IronPDF object model?

IPdfPathObjectCollection is in the IronSoftware namespace, shipped in IronPdf.dll. It extends IDocumentPathObjectCollection . Concrete classes such as PathObjectCollection implement it.

Interface IPdfPathObjectCollection

Q: What implements IPdfPathObjectCollection in IronPDF?

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

Collection of PDF path objects

Namespace: IronSoftware

Assembly: IronPdf.dll

Syntax

public interface IPdfPathObjectCollection

Use IPdfPathObjectCollection in IronPDF when C# code works with Iron Software API across implementors. It represents collection of PDF path objects, so code can work with Iron Software API uniformly across implementors rather than binding to a concrete type.

Concrete implementors include PathObjectCollection, IronPDF concrete implementor. Code that accepts IPdfPathObjectCollection 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 IPdfPathObjectCollection contract members, the IPdfPathObjectCollection contract members; consult these first when implementing or consuming IPdfPathObjectCollection.

using IronPdf;

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