Book Image

Improving your C# Skills

By : Ovais Mehboob Ahmed Khan, John Callaway, Clayton Hunt, Rod Stephens
Book Image

Improving your C# Skills

By: Ovais Mehboob Ahmed Khan, John Callaway, Clayton Hunt, Rod Stephens

Overview of this book

This Learning Path shows you how to create high performing applications and solve programming challenges using a wide range of C# features. You’ll begin by learning how to identify the bottlenecks in writing programs, highlight common performance pitfalls, and apply strategies to detect and resolve these issues early. You'll also study the importance of micro-services architecture for building fast applications and implementing resiliency and security in .NET Core. Then, you'll study the importance of defining and testing boundaries, abstracting away third-party code, and working with different types of test double, such as spies, mocks, and fakes. In addition to describing programming trade-offs, this Learning Path will also help you build a useful toolkit of techniques, including value caching, statistical analysis, and geometric algorithms. This Learning Path includes content from the following Packt products: • C# 7 and .NET Core 2.0 High Performance by Ovais Mehboob Ahmed Khan • Practical Test-Driven Development using C# 7 by John Callaway, Clayton Hunt • The Modern C# Challenge by Rod Stephens
Table of Contents (26 chapters)
Title Page
Copyright and Credits
About Packt
What to Know Before Getting Started
Files and Directories
Advanced C# and .NET Features

Implementing a real API service

The time has come to actually receive data from the server. Our current data model is still not 100% correct, but the groundwork is there. When we receive the correct data structure from the server, we will need to update our views accordingly. We will leave that part as an exercise for you.

In this section, we will look at pulling our mocked API out of the factory that we created and replacing it with a real API. In our existing tests, we will use Sinon to override the default functionality of our Ajax component with the functionality from our mock API.

Lastly, we will need to create an application configuration object to manage the base path for the API to determine the correct path in both dev and prod.

Replacing the mock API with the real API service

To keep things as simple as possible, we will be using the fetch API to get data from the server. We will begin by breaking all the tests that are currently using the mock API. That is because we are going to...