How do you use IPdfFontObjectCollection in C# code?

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

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

Where is IPdfFontObjectCollection located in the IronPDF object model?

IPdfFontObjectCollection is in the IronSoftware namespace, shipped in IronPdf.dll. It extends IDocumentFontObjectCollection.

Interface IPdfFontObjectCollection

Q: What implements IPdfFontObjectCollection in IronPDF?

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

Collection of PDF font objects

Namespace: IronSoftware

Assembly: IronPdf.dll

Syntax

public interface IPdfFontObjectCollection

IPdfFontObjectCollection is the contract IronPDF C# code works through for Iron Software API. It represents collection of PDF font objects, so code can work with Iron Software API uniformly across implementors rather than binding to a concrete type.

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

using IronPdf;

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