AspNetCore.Docs/aspnetcore/grpc/code-first.md

title	author	description	monikerRange	ms.author	ms.date	no-loc	uid
Code-first gRPC services and clients with .NET	jamesnk	Learn the basic concepts when writing code-first gRPC with .NET.	>= aspnetcore-3.0	jamesnk	01/04/2021	Home Privacy Kestrel appsettings.json ASP.NET Core Identity cookie Cookie Blazor Blazor Server Blazor WebAssembly Identity Let's Encrypt Razor SignalR	grpc/code-first

Code-first gRPC services and clients with .NET

By James Newton-King and Marc Gravell

Code-first gRPC uses .NET types to define service and message contracts.

Code-first is a good choice when an entire system uses .NET:

• .NET service and data contract types can be shared between the .NET server and clients.
• Avoids the need to define contracts in .proto files and code generation.

Code-first isn't recommended in polyglot systems with multiple languages. .NET service and data contract types can't be used with non-.NET platforms. To call a gRPC service written using code-first, other platforms must create a .proto contract that matches the service.

protobuf-net.Grpc

[!IMPORTANT] For help with protobuf-net.Grpc, visit the protobuf-net.Grpc website or create an issue on the protobuf-net.Grpc GitHub repository.

protobuf-net.Grpc is a community project and isn't supported by Microsoft. It adds code-first support to Grpc.AspNetCore and Grpc.Net.Client. It uses .NET types annotated with attributes to define an app's gRPC services and messages.

The first step to creating a code-first gRPC service is defining the code contract:

• Create a new project that will be shared by the server and client.
• Add a protobuf-net.Grpc package reference.
• Create service and data contract types.

[!code-csharp]

The preceding code:

• Defines HelloRequest and HelloReply messages.
• Defines the IGreeterService contract interface with the unary SayHelloAsync gRPC method.

The service contract is implemented on the server and called from the client. Methods defined on service interfaces must match certain signatures depending on whether they're unary, server streaming, client streaming, or bidirectional streaming.

For more information on defining service contracts, see the protobuf-net.Grpc getting started documentation.

Create a code-first gRPC service

To add gRPC code-first service to an ASP.NET Core app:

• Add a protobuf-net.Grpc.AspNetCore package reference.
• Add a reference to the shared code-contract project.

Create a new GreeterService.cs file and implement the IGreeterService service interface:

[!code-csharp]

Update the Startup.cs file:

[!code-csharp]

In the preceding code:

• AddCodeFirstGrpc registers services that enable code-first.
• MapGrpcService<GreeterService> adds the code-first service endpoint.

gRPC services implemented with code-first and .proto files can co-exist in the same app. All gRPC services use gRPC service configuration.

Create a code-first gRPC client

A code-first gRPC client uses the service contract to call gRPC services. To call a gRPC service using a code-first client:

• Add a protobuf-net.Grpc package reference.
• Add a reference to the shared code-contract project.
• Add a Grpc.Net.Client package reference.

[!code-csharp]

The preceding code:

• Creates a gRPC channel.
• Creates a code-first client from the channel with the CreateGrpcService<IGreeterService> extension method.
• Calls the gRPC service with SayHelloAsync.

A code-first gRPC client is created from a channel. Just like a regular client, a code-first client uses its channel configuration.

View or download sample code (how to download)

Additional resources

• protobuf-net.Grpc website
• protobuf-net.Grpc GitHub repository