Book Image

Clean Code in C#

By : Jason Alls
Book Image

Clean Code in C#

By: Jason Alls

Overview of this book

Traditionally associated with developing Windows desktop applications and games, C# is now used in a wide variety of domains, such as web and cloud apps, and has become increasingly popular for mobile development. Despite its extensive coding features, professionals experience problems related to efficiency, scalability, and maintainability because of bad code. Clean Code in C# will help you identify these problems and solve them using coding best practices. The book starts with a comparison of good and bad code, helping you understand the importance of coding standards, principles, and methodologies. You’ll then get to grips with code reviews and their role in improving your code while ensuring that you adhere to industry-recognized coding standards. This C# book covers unit testing, delves into test-driven development, and addresses cross-cutting concerns. You’ll explore good programming practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. Once you’ve studied API design and discovered tools for improving code quality, you’ll look at examples of bad code and understand which coding practices you should avoid. By the end of this clean code book, you’ll have the developed skills you need in order to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (17 chapters)

Building your own custom exceptions

Microsoft .NET Framework already has a good number of exceptions that can be raised that you are able to trap. But there may be instances where you'll require a custom exception that provides more detailed information or that is more end user friendly in its terminology.

So, we are now going to look at what the requirements are for building our own custom exceptions. It is surprisingly simple to build your own custom exception. All you have to do is give your class a name that ends with Exception and inherit from System.Exception. Then, you need to add three constructors, as shown in the following code example:

    public class TickerListNotFoundException : Exception
{
public TickerListNotFoundException() : base()
{
}

public TickerListNotFoundException(string message)
: base(message)
{
}

public TickerListNotFoundException(
string message,
...