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

Chapter 2. Cricket Score Calculator and Tracker

Object-oriented programming (OOP) is a crucial element of writing .NET applications. Proper OOP ensures that developers can share code easily between projects. You don't have to rewrite code that has already been written. This is called inheritance.

A lot has been written throughout the years on the topic of OOP. In fact, doing a search on the internet on the benefits of OOP will return countless results. The fundamental benefits of OOP, however, are the modular approach to writing code, the ease with which code can be shared, and the ability to extend the functionality of shared code.

These little building blocks (or classes) are self-contained units of code that each perform a function. Developers do not need to know what goes on inside the class when they use it. They can just assume that the class will function on its own and will always work. Should the class they implement not provide a specific functionality, the developer is free to extend...