Book Image

High-Performance Programming in C# and .NET

By : Jason Alls
Book Image

High-Performance Programming in C# and .NET

By: Jason Alls

Overview of this book

Writing high-performance code while building an application is crucial, and over the years, Microsoft has focused on delivering various performance-related improvements within the .NET ecosystem. This book will help you understand the aspects involved in designing responsive, resilient, and high-performance applications with the new version of C# and .NET. You will start by understanding the foundation of high-performance code and the latest performance-related improvements in C# 10.0 and .NET 6. Next, you’ll learn how to use tracing and diagnostics to track down performance issues and the cause of memory leaks. The chapters that follow then show you how to enhance the performance of your networked applications and various ways to improve directory tasks, file tasks, and more. Later, you’ll go on to improve data querying performance and write responsive user interfaces. You’ll also discover how you can use cloud providers such as Microsoft Azure to build scalable distributed solutions. Finally, you’ll explore various ways to process code synchronously, asynchronously, and in parallel to reduce the time it takes to process a series of tasks. By the end of this C# programming book, you’ll have the confidence you need to build highly resilient, high-performance applications that meet your customer's demands.
Table of Contents (22 chapters)
1
Part 1: High-Performance Code Foundation
7
Part 2: Writing High-Performance Code
16
Part 3: Threading and Concurrency

Performing static code analysis

The purpose of static code analysis is to help you improve your overall architectural quality, code quality, and performance by doing the following:

  • Visualizing software architecture and its software dependencies
  • Enforcing the designated architectural rules regarding laying, subsystems, calling rules, and more
  • Identifying code that has been cloned and modified using cut, copy, and paste
  • Identifying dead code that can be removed
  • Calculating various software metrics
  • Performing code style checks and flagging violations

Many companies employ static code analysis as part of their Continuous Integration (CI) process. There are various stages at which problems can come to light. These stages are listed as follows:

  • When compiling source code in the IDE
  • When running unit tests and end-to-end system tests
  • When pushing source code to version control and issuing a pull request
  • When a pull request has been issued...