Book Image

Building Blazor WebAssembly Applications with gRPC

By : Václav Pekárek
5 (1)
Book Image

Building Blazor WebAssembly Applications with gRPC

5 (1)
By: Václav Pekárek

Overview of this book

Building Blazor WebAssembly Applications with gRPC will take you to the next level in your web development career. After working through all the essentials of gRPC, Blazor, and source generators, you will be far from a beginner C# developer and would qualify as a developer with intermediate knowledge of the Blazor ecosystem. After a quick primer on the basics of Blazor technology, REST, gRPC, and source generators, you’ll dive straight into building Blazor WASM applications. You’ll learn about everything from two-way bindings and Razor syntax to project setup. The practical emphasis continues throughout the book as you steam through creating data repositories, working with REST, and building and registering gRPC services. The chapters also cover how to manage source generators, C# and debugging best practices, and more. There is no shorter path than this book to solidify your gRPC-enabled web development knowledge. By the end of this book, your knowledge of building Blazor applications with one of the most modern and powerful frameworks around will equip you with a highly sought-after skill set that you can leverage in the best way possible.
Table of Contents (10 chapters)

Understanding the protocol buffer language

The Google Protocol Buffer language (sometimes called protocol buffer language) is used to describe the structure of protocol buffer data. The language is currently in version 3 and the .proto files should have directives at the top of the file specifying the version of the language used in the file (the current version is proto3). The file can also have a package name for sharing the files between applications.

The following code shows the basic directive definition of the file:

syntax = "proto3";
package grpc;

In the preceding code, we are using the syntax directive to specify the version and the package directive to specify the name of the package.

When we want to extend the package functionality, we can use the option and import directives:

option csharp_namespace = "MediaLibrary.Contracts";
import "different_file.proto";

In the preceding code, we are using the option directive to specify...