Book Image

Mastering Entity Framework Core 2.0

By : Prabhakaran Anbazhagan
Book Image

Mastering Entity Framework Core 2.0

By: Prabhakaran Anbazhagan

Overview of this book

Being able to create and maintain data-oriented applications has become crucial in modern programming. This is why Microsoft came up with Entity Framework so architects can optimize storage requirements while also writing efficient and maintainable application code. This book is a comprehensive guide that will show how to utilize the power of the Entity Framework to build efficient .NET Core applications. It not only teaches all the fundamentals of Entity Framework Core but also demonstrates how to use it practically so you can implement it in your software development. The book is divided into three modules. The first module focuses on building entities and relationships. Here you will also learn about different mapping techniques, which will help you choose the one best suited to your application design. Once you have understood the fundamentals of the Entity Framework, you will move on to learn about validation and querying in the second module. It will also teach you how to execute raw SQL queries and extend the Entity Framework to leverage Query Objects using the Query Object Pattern. The final module of the book focuses on performance optimization and managing the security of your application. You will learn to implement failsafe mechanisms using concurrency tokens. The book also explores row-level security and multitenant databases in detail. By the end of the book, you will be proficient in implementing Entity Framework on your .NET Core applications.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Dedication
Preface
4
Building Relationships – Understanding Mapping

Url field validation


We will look into Url validation, how it should be configured, and how it works with the MVC engine. It does the basic syntax check on the URL value rather than verifying the URL itself, so it would be ideal to have a consistent mechanism to perform, such as verification, to have uniform behavior between systems. The Url validation is performed based on the pattern -

 <protocol>://<domain-name>.<extension> . Let's explore the pattern in detail:

  • Protocol: It should be HTTP, https, or FTP
  • Domain name: It should be one or more characters
  • Extension: It should be two or more characters (for instance, http://a.bc is valid since it follows the preceding pattern)

The Url attribute/data annotation can be used in the following ways:

    public class Blog
    {
      // Code removed for brevity
      [Required(ErrorMessage = "Url is required")]
[Url]
      public string Url { get; set; }
    }

The Url validation reports the following value as the error The Url field...