Book Image

C# 7 and .NET Core 2.0 Blueprints

By : Dirk Strauss, Jas Rademeyer
Book Image

C# 7 and .NET Core 2.0 Blueprints

By: Dirk Strauss, Jas Rademeyer

Overview of this book

.NET Core is a general purpose, modular, cross-platform, and open source implementation of .NET. With the latest release of .NET Core, many more APIs are expected to show up, which will make APIs consistent across .Net Framework, .NET Core, and Xamarin. This step-by-step guide will teach you the essential .NET Core and C# concepts with the help of real-world projects. The book starts with a brief introduction to the latest features of C# 7 and .NET Core 2.0 before moving on to explain how C# 7 can be implemented using the object-oriented paradigm. You'll learn to work with relational data using Entity Framework and see how to use ASP.NET Core practically. This book will show you how .NET Core allows the creations of cross-platform applications. You'll also learn about SignalR to add real-time functionality to your application. Then you will see how to use MongoDB and how to implement MongoDB into your applications. You'll learn about serverless computing and OAuth concepts, along with running ASP.NET Core applications with Docker Compose. This project-based guide uses practical applications to demonstrate these concepts. By the end of the book, you'll be proficient in developing applications using .NET Core 2.0.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Packt Upsell

Developing a database design

We can't know what we're doing until we know what we're doing. Before we jump in and create a Solution with our database, models, and controllers, we need to first figure out how we want to design the database.

According to Microsoft's TechNet, there are five basic steps one could follow to plan a database:

  1. Gather information
  2. Identify the objects
  3. Model the objects
  4. Identify the types of information for each object
  5. Identify the relationship between objects

Our requirement is pretty simple. We only need to save a web link to navigate to later, so we won't have multiple objects with relationships between them.

We do, however, need to clarify the types of information we'd like to save for our object (web link). Obviously, we need the URL, but what else do we need? Make sure you understand what information is required for your Solution and how it will be used.

Think about it in everyday terms—if you write an address for a friend's house, you might want something more that just...