Book Image

Code-First Development with Entity Framework

By : Sergey Barskiy
Book Image

Code-First Development with Entity Framework

By: Sergey Barskiy

Overview of this book

<p>Entity Framework Code-First enables developers to read and write data in a relational database system using C# or VB.NET. It is Microsoft's answer to demand for an ORM from .NET developers.</p> <p>This book will help you acquire the necessary skills to program your applications using Entity Framework. You will start with database configuration and learn how to write classes that define the database structure. You will see how LINQ can be used with Entity Framework to give you access to stored data. You will then learn how to use Entity Framework to persist information in a Relational Database Management System. You will also see how you can benefit from writing ORM-based .NET code. Finally, you will learn how Entity Framework can help you to solve database deployment problems using migrations.</p>
Table of Contents (15 chapters)
Code-First Development with Entity Framework
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Chapter 3: Defining the Database Structure


Q1. If you want to make a value optional, you need to use nullable types in Entity Framework. As we need to store an integer value, the correct answer is Int.

Q2. The statement is false because the string is a nullable type in .NET. Hence, by default the column will be nullable as well.

Q3. The statement is false. You can remove the conventions from the Entity Framework configuration using the Remove method on the Conventions collection in the model builder.

Q4. Many-to-Default is not a relationship type. One-to-Many (or One-to-Zero-to-Many), One-to-One (or One-to-Zero-to-One), and Many-to-Many are the correct relationship types.

Q5. The answer is false. This approach will become unwieldy if you have many tables in the database.

Q6. By default, Entity Framework will use Unicode types, such as nvarchar for string properties. As there are no constraints on the string property, the correct type will be nvarchar(max).

Q7. Domain is not a relationship type.

Q8. EntityTypeConfiguration is the correct "buddy" class to be used to configure persistence for an entity.