Book Image

Learn C# Programming

By : Marius Bancila, Raffaele Rialdi, Ankit Sharma
5 (1)
Book Image

Learn C# Programming

5 (1)
By: Marius Bancila, Raffaele Rialdi, Ankit Sharma

Overview of this book

The C# programming language is often developers’ primary choice for creating a wide range of applications for desktop, cloud, and mobile. In nearly two decades of its existence, C# has evolved from a general-purpose, object-oriented language to a multi-paradigm language with impressive features. This book will take you through C# from the ground up in a step-by-step manner. You'll start with the building blocks of C#, which include basic data types, variables, strings, arrays, operators, control statements, and loops. Once comfortable with the basics, you'll then progress to learning object-oriented programming concepts such as classes and structures, objects, interfaces, and abstraction. Generics, functional programming, dynamic, and asynchronous programming are covered in detail. This book also takes you through regular expressions, reflection, memory management, pattern matching, exceptions, and many other advanced topics. As you advance, you'll explore the .NET Core 3 framework and learn how to use the dotnet command-line interface (CLI), consume NuGet packages, develop for Linux, and migrate apps built with .NET Framework. Finally, you'll understand how to run unit tests with the Microsoft unit testing frameworks available in Visual Studio. By the end of this book, you’ll be well-versed with the essentials of the C# language and be ready to start creating apps with it.
Table of Contents (20 chapters)

Consuming NuGet packages

Packages play a very important role in modern application development because they define a self-contained unit of code that can be used as a brick to build larger applications.

This same definition was used in the past for libraries composed by a single .dll file, but modern development often requires more files to make a unit of code that's properly self-contained. The simplest example is when a package contains the library as well as its dependencies, but another, more complex, example is writing a library needing platform invocation calls to native APIs.

Native interoperability can also be written in a single library by using the aforementioned RuntimeInformation class, but it is generally better for both performance and maintenance to split the code into one library for each OS and CPU architecture. The advantage of packaging the platform-dependent libraries is that it lets the .NET Core build tools copy the relevant library in the output folder...