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)

Exceptions

Exceptions are a mechanism provided by the runtime to make the execution suddenly interrupt and jump to the code handling the error. Since the handler may have been declared by any caller in the calling path, the runtime takes care of restoring the stack and any other outstanding finally block, which we will examine in the The finally block section of this chapter.

The calling code may want to handle the exception and if it does, it may decide to resume normal execution or just let the exception continue to the other handlers (if any). Whenever no handling code is provided by the application, the runtime catches the error condition and does the only reasonable thing—it terminates the application.

This brings us back to the original question that we asked in the introduction—is the exception part of the contract between the library implementor and its consumer, or is it rather an implementation detail?

Since the implementor communicates an anomaly to...