- inside front cover
- Code like a Pro in C#
- Copyright
- contents
- front matter
- Part 1 Using C# and .NET
- 1 Introducing C# and .NET
- 1.1 Why work in C#?
- 1.1.1 Reason 1: C# is economical
- 1.1.2 Reason 2: C# is maintainable
- 1.1.3 Reason 3: C# is developer friendly and easy to use
- 1.2 Why not work in C#?
- 1.2.1 Operating system development
- 1.2.2 Real-time operating system embedded development in C#
- 1.2.3 Numerical computing and C#
- 1.3 Switching to C#
- 1.4 What you will learn in this book
- 1.5 What you will not learn in this book
- Summary
- 2 .NET and how it compiles
- Part 2 The existing codebase
- 3 How bad is this code?
- 3.1 Introducing Flying Dutchman Airlines
- 3.2 Pieces of the puzzle: Taking a look at our requirements
- 3.2.1 Object-relational mapping
- 3.2.2 The GET /flight endpoint: Retrieving information on all flights
- 3.2.3 The GET /flight/{flightNumber} endpoint: Getting specific flight information
- 3.2.4 The POST /booking/{flightNumber} endpoint: Booking a flight
- 3.3 Coming to terms with the existing codebase
- 3.3.1 Assessing the existing database schema and its tables
- 3.3.2 The existing codebase: Web service configuration files
- 3.3.3 Considering models and views in the existing codebase
- Summary
- 4 Manage your unmanaged resources!
- 4.1 The FlightController: Assessing the GET /flight endpoint
- 4.1.1 The GET /flight endpoint and what it does
- 4.1.2 Method signature: The meaning of ResponseType and typeof
- 4.1.3 Collecting flight information with collections
- 4.1.4 Connection strings, or how to give a security engineer a heart attack
- 4.1.5 Using IDisposable to release unmanaged resources
- 4.1.6 Querying a database with SqlCommand
- 4.2 The FlightController: Assessing GET /flight/{flightNumber}
- 4.3 The FlightController: POST /flight
- 4.4 The FlightController: DELETE /flight/{flightNumber}
- Exercises
- Summary
- Part 3 The database access layer
- 5 Setting up a project and database with Entity Framework Core
- 5.1 Creating a .NET 5 solution and project
- 5.2 Setting up and configuring a web service
- 5.2.1 Configuring a .NET 5 web service
- 5.2.2 Creating and using HostBuilder
- 5.2.3 Implementing the Startup class
- 5.2.4 Using the repository/service pattern for our web service architecture
- 5.3 Implementing the database access layer
- 5.3.1 Entity Framework Core and reverse-engineering
- 5.3.2 DbSet and the Entity Framework Core workflow
- 5.3.3 Configuration methods and environment variables
- 5.3.4 Setting an environment variable on Windows
- 5.3.5 Setting an environment variable on macOS
- 5.3.6 Retrieving environment variables at run time in your code
- Exercises
- Summary
- Part 4 The repository layer
- 6 Test-driven development and dependency injection
- 6.1 Test-driven development
- Exercises
- 6.2 The CreateCustomer method
- 6.2.1 Why you should always validate input arguments
- 6.2.2 Using “arrange, act, assert” to write unit tests
- 6.2.3 Validating against invalid characters
- 6.2.4 In-lining test data with the [DataRow] attribute
- 6.2.5 Object initializers and autogenerated code
- 6.2.6 Constructors, reflection, and asynchronous programming
- 6.2.7 Locks, mutexes, and semaphores
- 6.2.8 Synchronous to asynchronous execution . . . continued
- 6.2.9 Testing Entity Framework Core
- 6.2.10 Controlling dependencies with dependency injection
- Exercises
- Summary
- 7 Comparing objects
- 7.1 The GetCustomerByName method
- 7.1.1 Question marks: Nullable types and their applications
- 7.1.2 Custom exceptions, LINQ, and extension methods
- 7.2 Congruence: From the Middle Ages to C#
- 7.2.1 Creating a “comparer” class using EqualityComparer<T>
- 7.2.2 Testing equality by overriding the Equals method
- 7.2.3 Overloading the equality operator
- Exercises
- Summary
- 8 Stubbing, generics, and coupling
- 8.1 Implementing the Booking repository
- 8.2 Input validation, separation of concerns, and coupling
- Exercises
- 8.3 Using object initializers
- 8.4 Unit testing with stubs
- 8.5 Programming with generics
- 8.6 Providing default arguments by using optional parameters
- 8.7 Conditionals, Func, switches, and switch expressions
- 8.7.1 The ternary conditional operator
- 8.7.2 Branching using an array of functions
- 8.7.3 Switch statements and expressions
- 8.7.4 Querying for pending changes in Entity Framework Core
- Exercises
- Summary
- 9 Extension methods, streams, and abstract classes
- 9.1 Implementing the Airport repository
- 9.2 Getting an Airport out of the database by its ID
- 9.3 Validating the AirportID input parameter
- 9.4 Output streams and being specifically abstract
- 9.5 Querying the database for an Airport object
- 9.6 Implementing the Flight repository
- 9.6.1 The IsPositive extension method and “magic numbers”
- 9.6.2 Getting a flight out of the database
- Exercises
- Summary
- Part 5 The service layer
- 10 Reflection and mocks
- 10.1 The repository/service pattern revisited
- 10.1.1 What is the use of a service class?
- Exercises
- 10.2 Implementing the CustomerService
- 10.2.1 Setting up for success: Creating skeleton classes
- 10.2.2 How to delete your own code
- Exercises
- 10.3 Implementing the BookingService
- 10.3.1 Unit testing across architectural layers
- 10.3.2 The difference between a stub and a mock
- 10.3.3 Mocking a class with the Moq library
- 10.3.4 Calling a repository from a service
- Exercises
- Summary
- 11 Runtime type checking revisited and error handling
- 11.1 Validating input parameters of a service layer method
- 11.1.1 Runtime type checks with the is and as operators
- 11.1.2 Type checking with the is operator
- 11.1.3 Type checking with the as operator
- 11.1.4 What did we do in section 11.1?
- 11.2 Cleaning up the BookingServiceTests class
- 11.3 Foreign key constraints in service classes
- 11.3.1 Calling the Flight repository from a service class
- Exercises
- Summary
- 12 Using IAsyncEnumerable<T> and yield return
- 12.1 Do we need an AirportService class?
- 12.2 Implementing the FlightService class
- 12.2.1 Getting information on a specific flight from the FlightRepository
- 12.2.2 Combining two data streams into a view
- 12.2.3 Using the yield return keywords with try-catch code blocks
- 12.2.4 Implementing GetFlightByFlightNumber
- Exercises
- Summary
- Part 6 The controller layer
- 13 Middleware, HTTP routing, and HTTP responses
- 13.1 The controller class within the repository/service pattern
- 13.2 Determining what controllers to implement
- 13.3 Implementing the FlightController
- 13.3.1 Returning HTTP responses with the IActionResult interface (GetFlights)
- 13.3.2 Injecting dependencies into a controller using middleware
- 13.3.3 Implementing the GET /Flight/{FlightNumber} endpoint
- 13.4 Routing HTTP requests to controllers and methods
- Exercises
- Summary
- 14 JSON serialization/ deserialization and custom model binding
- 14.1 Implementing the BookingController class
- 14.1.1 Introduction to data deserialization
- 14.1.2 Using the [FromBody] attribute to deserialize incoming HTTP data
- 14.1.3 Using a custom model binder and method attribute for model binding
- 14.1.4 Implementing the CreateBooking endpoint method logic
- 14.2 Acceptance testing and Swagger middleware
- 14.2.1 Manual acceptance testing with an OpenAPI specification
- 14.2.2 Generating an OpenAPI specification at runtime
- 14.3 The end of the road
- Summary
- appendix A Exercise answers
- Chapter 2: .NET and how it compiles
- Chapter 4: Manage your unmanaged resources!
- Chapter 5: Setting up a project and database with Entity Framework Core
- Chapter 6: Test-driven development and dependency injection
- Chapter 7: Comparing objects
- Chapter 8: Stubbing, generics, and coupling
- Chapter 9: Extension methods, streams, and abstract classes
- Chapter 10: Reflection and mocks
- Chapter 11: Runtime type checking revisited and error handling
- Chapter 12: Using IAsyncEnumerable<T> and yield return
- Chapter 13: Middleware, HTTP routing, and HTTP responses
- appendix B Clean code checklist
- appendix C Installation guides
- appendix D OpenAPI FlyTomorrow
- appendix E Reading list
- index
- inside back cover
After reading part 1, you are familiar with C# and the various flavors of the .NET Framework. You know how C# is compiled and why you would (or would not) want to use it for your own projects. In this part, I’ll introduce you to Flying Dutchman Airlines. This company acts as our business case throughout the rest of the book.
In the next two chapters, we’ll work on an existing codebase and examine it in depth, taking stock of where we can make improvements and why.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.