Search Results for

    Show / Hide Table of Contents

    Namespace IronPdf.GrpcLayer

    Classes

    IronPdfConnectionConfiguration

    Configures the connection to IronPdfEngine for distributed/remote PDF processing. Use static factory methods for common configurations.

    IronPdfEngine can run locally, in Docker, or on remote servers for scalable PDF generation across distributed architectures.

    Example - Configuration scenarios:

    // Docker container (common for microservices):
    IronPdf.Setting.Connection = IronPdfConnectionConfiguration.Docker;
    

    // Remote server with custom port: IronPdf.Setting.Connection = IronPdfConnectionConfiguration.RemoteServer( "https://pdf-server.mycompany.com:8080");

    // .NET Framework with custom channel: IronPdf.Setting.Connection = IronPdfConnectionConfiguration.NetFrameworkChannel( "192.168.1.100:33350");

    // Custom gRPC channel with metadata: var channel = GrpcChannel.ForAddress("https://secure-server.com"); var metadata = new Metadata { { "Authorization", "Bearer token123" } }; IronPdf.Setting.Connection = IronPdfConnectionConfiguration.WithCustomChannel( channel, metadata);

    IronPdfConnectionType

    Specifies how IronPDF connects to the rendering engine (IronPdfEngine). Choose based on your deployment architecture.

    Example - Configure connection:

    // Local executable (default):
    Installation.ConnectionType = IronPdfConnectionType.LocalExecutable;
    

    // Docker container: IronPdf.Setting.Connection = IronPdfConnectionConfiguration.Docker;

    // Remote server: IronPdf.Setting.Connection = IronPdfConnectionConfiguration.RemoteServer( "https://my-ironpdf-server.com:33350");

    ☀
    ☾
    Downloads
    • Download with Nuget
    • Start for Free
    In This Article
    Back to top
    Install with Nuget