Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Clean Code with C#
  • Table Of Contents Toc
  • Feedback & Rating feedback
Clean Code with C#

Clean Code with C#

By : Jason Alls
4.5 (2)
close
close
Clean Code with C#

Clean Code with C#

4.5 (2)
By: Jason Alls

Overview of this book

Traditionally associated with Windows desktop applications and game development, C# has expanded into web, cloud, and mobile development. However, despite its extensive coding features, professionals often encounter issues with efficiency, scalability, and maintainability due to poor code. Clean Code in C# guides you in identifying and resolving these problems using coding best practices. This book starts by comparing good and bad code to emphasize the importance of coding standards, principles, and methodologies. It then covers code reviews, unit testing, and test-driven development, and addresses cross-cutting concerns. As you advance through the chapters, you’ll discover programming best practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. You’ll also explore API design and code quality enhancement tools, while studying examples of poor coding practices to understand what to avoid. By the end of this clean code book, you’ll have the developed the skills needed to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (18 chapters)
close
close

TDD

TDD is a software development approach in which tests are written before the actual code. The process involves iterative cycles: write a small unit test, run it (expecting it to fail initially), then write the code to make the test pass, and finally refactor the code while ensuring that all tests continue to pass. This cycle is often summarized as Red-Green-Refactor.

The reason why TDD is needed is that it enables early detection of defects, helps produce clearer requirements, facilitates incremental development, and enables developers to refactor with confidence.

By writing tests before writing the actual code, developers are forced to consider the desired functionality and potential edge cases. This helps catch defects at an early stage, reducing the cost and effort required for debugging later in the development cycle.

Writing tests before code encourages developers to think through the requirements and expected behavior of the system. This results in clearer and more...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY