Grpc.Core Build Errors After IronPDF 2026.11.1

Curtis Chau
Curtis Chau
Updated: November 5, 2026

IronPDF 2026.11.1 drops the deprecated Grpc.Core package from its .NET 6+ client and moves engine connections to the managed gRPC stack. Code that references Grpc.Core types such as Channel, GrpcEnvironment, or Grpc.Core.Logging no longer receives that package through IronPDF and fails to build, and Docker and LocalExecutable connections stop reading proxy environment variables.

error CS0234: The type or namespace name 'Channel' does not exist in the namespace 'Grpc.Core' (are you missing an assembly reference?)
error CS0234: The type or namespace name 'Logging' does not exist in the namespace 'Grpc.Core' (are you missing an assembly reference?)
error CS0246: The type or namespace name 'Channel' could not be found (are you missing a using directive or an assembly reference?)
Text

From 2026.11.1, the .NET 6 and .NET 8 builds use Grpc.Net.Client instead of the deprecated Grpc.Core, so Grpc.Core-only types no longer arrive through IronPDF. The new stack also stops Docker and LocalExecutable connections from reading grpc_proxy, https_proxy, or http_proxy, and RemoteServer connections from reading grpc_proxy.

.NET Framework and .NET Standard 2.0 projects still get Grpc.Core through IronPDF and are not affected.

Solution

Option 1: Build errors for Grpc.Core types on .NET 6+

The errors CS0234, CS0246, CS0103, and CS1061 affect these members: Channel, ChannelOption, ChannelState, GrpcEnvironment, Grpc.Core.Logging, and the ToListAsync / ForEachAsync extensions. The types ChannelBase, Metadata, ChannelCredentials, and RpcException still build.

Recommended: add a direct reference to Grpc.Core and your existing code builds again:

dotnet add package Grpc.Core
SHELL

If you would rather not take the dependency, remove Grpc.Core.Logging code that only existed for debugging, or replace a custom channel with a built-in preset such as IronPdfConnectionConfiguration.Docker.

Option 2: Engine traffic no longer goes through your proxy

This change is intended. Docker and LocalExecutable connections now go directly to the engine address even when a proxy variable is set. Confirm the application can reach the engine host and port directly, for example by running the engine on the same host or Docker network:

Installation.ConnectToIronPdfHost(IronPdfConnectionConfiguration.Docker);
C#

RemoteServer connections still use https_proxy, http_proxy, and the Windows system proxy. If you set the proxy only in grpc_proxy, move it to https_proxy or http_proxy. With WithCustomChannel, your own channel's proxy settings apply.

References

Curtis Chau holds a Bachelor’s degree in Computer Science (Carleton University) and specializes in front-end development with expertise in Node.js, TypeScript, JavaScript, and React. Passionate about crafting intuitive and aesthetically pleasing user interfaces, Curtis enjoys working with modern frameworks and creating well-structured, visually appealing manuals.

Read More

Ready to Get Started?

NuGet Downloads 22,198,312Version:2026.11just released