You're reading from Web Development with Blazor A hands-on guide for .NET developers to build interactive UIs with C#

Product type Paperback

Published in Jun 2021

Publisher Packt

ISBN-13 9781800208728

Length 310 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Front End Web Development

Author (1):

Jimmy Engström

View More author details

Table of Contents (20) Chapters

Preface

1. Section 1:The Basics

2. Chapter 1: Hello Blazor FREE CHAPTER

3. Chapter 2: Creating Your First Blazor App

4. Section 2:Building an Application with Blazor

5. Chapter 3: Introducing Entity Framework Core

6. Chapter 4: Understanding Basic Blazor Components

7. Chapter 5: Creating Advanced Blazor Components

8. Chapter 6: Building Forms with Validation

9. Chapter 7: Creating an API

10. Chapter 8: Authentication and Authorization

11. Chapter 9: Sharing Code and Resources

12. Chapter 10: JavaScript Interop

13. Chapter 11: Managing State

14. Section 3:Debug, Test, and Deploy

15. Chapter 12: Debugging

16. Chapter 13: Testing

17. Chapter 14: Deploy to Production

18. Chapter 15: Where to Go from Here

19. Other Books You May Enjoy

Packt is searching for authors like you

Storing data on the server side

There are many different ways in which to store data on the server side. The only thing to remember is that Blazor WebAssembly will always need an API. Blazor Server doesn't need an API since we can access the server-side resourcesdirectly.

I have had discussions with many developers when it comes to APIs or direct access and it all boils down to what you intend to do with the application. If you are building a Blazor Server application and have no interest in moving to Blazor WebAssembly, I would probably go for direct access, as we have done in the MyBlog project.

I would not do direct database queries in the components though. I would keep it in an API, just not a Web API. As we have seen, exposing those API functions in an API, as we did in Chapter 7, Creating an API, and Chapter 9, Sharing Code and Resources, is not a lot of steps. We can always start with direct sever access and move to an API if we want to.

When it comes to ways...