Learning Blazor

Chapter 3. ​​Componentizing

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the third chapter of the final book.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

Our app has lifted off and taken flight — Hooray! We’re going to continue our adventure of learning Blazor by scrutinizing code. In this chapter, you’ll learn how to author Blazor components and various data-binding approaches. Now that you’re familiar with how the app starts, we’ll evaluate the default route of the app. This just so happens to serve the Index.razor file, which is the home screen for the app. You’ll learn how to limit what a user has access to, by protecting components with declarative attributes and security-semantic hierarchies. You’ll see native JavaScript geolocation services in use with JavaScript interop. As part of this chapter, you’ll also learn about some of the peripheral services and supporting architecture that the Blazor app relies on, such as; the “Have I Been Pwned” service and Open Weather Map APIs.

Design With The User In Mind

All graphical-based applications have users, but not all applications prioritize the needs of their ...