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)

Asynchronous Dispose

After the advent of Tasks in .NET, most of the libraries managing I/O operations progressively moved to an asynchronous behavior. For example, the System.Net.Websocket class members embrace the Task-based programming strategy, providing a better developer experience and more efficient behavior.

Every time a developer needs to write a C# client to access some service based on the WebSocket protocol, they typically write a wrapper class exposing specialized send methods and implementing the dispose pattern to invoke the Websocket.CloseAsync method. We also know that any asynchronous method should return a Task, but the Dispose method has been defined as void far before the Task era, and therefore doesn't fit well in the Task chain.

The Websocket example is very realistic as I had this exact problem some time ago, where blocking the current thread to wait for the CloseAsync to finish inside the Dispose caused a deadlock.

Starting from C# 8 and .NET Core...