Book Image

C# 7.1 and .NET Core 2.0 ??? Modern Cross-Platform Development - Third Edition

By : Mark J. Price
Book Image

C# 7.1 and .NET Core 2.0 ??? Modern Cross-Platform Development - Third Edition

By: Mark J. Price

Overview of this book

C# 7.1 and .NET Core 2.0 – Modern Cross-Platform Development, Third Edition, is a practical guide to creating powerful cross-platform applications with C# 7.1 and .NET Core 2.0. It gives readers of any experience level a solid foundation in C# and .NET. The first part of the book runs you through the basics of C#, as well as debugging functions and object-oriented programming, before taking a quick tour through the latest features of C# 7.1 such as default literals, tuples, inferred tuple names, pattern matching, out variables, and more. After quickly taking you through C# and how .NET works, this book dives into the .NET Standard 2.0 class libraries, covering topics such as packaging and deploying your own libraries, and using common libraries for working with collections, performance, monitoring, serialization, files, databases, and encryption. The final section of the book demonstrates the major types of application that you can build and deploy cross-device and cross-platform. In this section, you'll learn about websites, web applications, web services, Universal Windows Platform (UWP) apps, and mobile apps. 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.
Table of Contents (31 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
2
Part 1 – C# 7.1
8
Part 2 – .NET Core 2.0 and .NET Standard 2.0
16
Part 3 – App Models
22
Summary
Index

Making types more reusable with generics


In 2005, with C# and .NET Framework 2.0, Microsoft introduced a feature named generics that enables your types to be more reusable, by allowing a programmer to pass types as parameters similar to how you can pass objects as parameters.

Making a generic type

First, let's see an example of a non-generic type, so that you can understand the problem that generics is designed to solve.

In the PacktLibrary project, add a new class named Thing, as shown in the following code, and note the following:

  • Thing has a field named Data of the object type
  • Thing has a method named Process that accepts an input parameter of the string type, and returns a string value

Note

If we wanted the Thing type to be flexible in .NET Framework 1.0, we would have to use the object type for the field.

using System;

namespace Packt.CS7
{
   public class Thing
   {
      public object Data = default(object);

      public string Process(string input)
      {
         if (Data == input)...