You're reading from Web API Development with ASP.NET Core 8

Product type Book

Published in Apr 2024

Publisher Packt

ISBN-13 9781804610954

Pages 804 pages

Edition 1st Edition

Languages

Concepts

Web Services

Author (1):

Xiaodi Yan

Table of Contents (20) Chapters

Preface

1. Chapter 1: Fundamentals of Web APIs

2. Chapter 2: Getting Started with ASP.NET Core Web APIs

3. Chapter 3: ASP.NET Core Fundamentals (Part 1)

4. Chapter 4: ASP.NET Core Fundamentals (Part 2)

5. Chapter 5: Data Access in ASP.NET Core (Part 1: Entity Framework Core Fundamentals)

6. Chapter 6: Data Access in ASP.NET Core (Part 2 – Entity Relationships)

7. Chapter 7: Data Access in ASP.NET Core (Part 3: Tips)

8. Chapter 8: Security and Identity in ASP.NET Core

9. Chapter 9: Testing in ASP.NET Core (Part 1 – Unit Testing)

10. Chapter 10: Testing in ASP.NET Core (Part 2 – Integration Testing)

11. Chapter 11: Getting Started with gRPC

12. Chapter 12: Getting Started with GraphQL

13. Chapter 13: Getting Started with SignalR

14. Chapter 14: CI/CD for ASP.NET Core Using Azure Pipelines and GitHub Actions

15. Chapter 15: ASP.NET Core Web API Common Practices

16. Chapter 16: Error Handling, Monitoring, and Observability

17. Chapter 17: Cloud-Native Patterns

18. Index

Why subscribe?

19. Other Books You May Enjoy

Understanding one-to-one relationships

A one-to-one relationship means that one entity has a relationship with only one entity of another type. For example, a bicycle requires one lock, which can only be used for that particular bicycle. Similarly, a person is only allowed to possess one driver’s license, which is designated for their use only. In our sample code, a Contact entity has only one Address entity, and an Address entity belongs to only one Contact entity. In the previous section, you learned how to configure a one-to-many relationship using the HasOne()/WithMany() and HasMany()/WithOne() methods. In this section, you will learn how to configure a one-to-one relationship using the HasOne() and WithOne() methods.

One-to-one configuration

In a one-to-one relationship, both sides have a reference navigation property. Technically, both sides have equal positions. However, to explicitly configure the relationship, we need to specify which side is the dependent side...