Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • C# 7 and .NET Core: Modern Cross-Platform Development
  • Toc
  • feedback
C# 7 and .NET Core: Modern Cross-Platform Development

C# 7 and .NET Core: Modern Cross-Platform Development

4.2 (11)
close
C# 7 and .NET Core: Modern Cross-Platform Development

C# 7 and .NET Core: Modern Cross-Platform Development

4.2 (11)

Overview of this book

If you want to build powerful cross-platform applications with C# 7 and .NET Core, then this book is for you. First, we’ll run you through the basics of C#, as well as object-oriented programming, before taking a quick tour through the latest features of C# 7 such as tuples, pattern matching, out variables, and so on. After quickly taking you through C# and how .NET works, we’ll dive into the .NET Standard 1.6 class libraries, covering topics such as performance, monitoring, debugging, serialization and encryption. The final section will demonstrate the major types of application that you can build and deploy cross-device and cross-platform. In this section, we’ll cover Universal Windows Platform (UWP) apps, web applications, mobile apps, and web services. Lastly, we’ll look at how you can package and deploy your applications so that they can be hosted on all of today’s most popular platforms, including Linux and Docker. By the end of the book, you’ll be armed with all the knowledge you need to build modern, cross-platform applications using C# and .NET Core.
Table of Contents (18 chapters)
close

Chapter 8 - Working with Databases Using Entity Framework Core

  1. Which .NET data provider would you use to work with Microsoft SQL Server 2012 Express Edition?
    • .NET Core Data Provider for SQL Server.
  2. When defining a DbContext class, what type would you use for the property that represents a table, for example, the Products property?
    • DbSet<T>, where T is the entity type, for example, Product.
    • For a Products property on another entity, for example, Category, that represents a one-to-many relationship between entities, use ICollection<T>, where T is the related entity type.
  3. What is the EF convention for primary keys?
    • The property named ID or ClassNameID is assumed to be the primary key. If the type of that property is any of the following, then the property is also marked as being an IDENTITY column: tinyint, smallint, int, bigint, guid.
  4. When would you use an annotation attribute in an entity class?
    • You would use an annotation attribute in an entity class when the conventions cannot work...
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete