Book Image

ASP.NET Core 5 and React - Second Edition

By : Carl Rippon
Book Image

ASP.NET Core 5 and React - Second Edition

By: Carl Rippon

Overview of this book

Microsoft’s .NET framework is a robust server-side framework, now even more powerful thanks to the recent unification of the Microsoft ecosystem with the .NET 5 framework. This updated second edition addresses these changes in the .NET framework and the latest release of React. The book starts by taking you through React and TypeScript components for building an intuitive single-page application and then shows you how to design scalable REST APIs that can integrate with a React-based frontend. Next, you’ll get to grips with the latest features, popular patterns, and tools available in the React ecosystem, including function-based components, React Router, and Redux. As you progress through the chapters, you'll learn how to use React with TypeScript to make the frontend robust and maintainable and cover key ASP.NET 5 features such as API controllers, attribute routing, and model binding to build a sturdy backend. In addition to this, you’ll explore API security with ASP.NET 5 identity and authorization policies and write reliable unit tests using both .NET and React, before deploying your app on Azure. By the end of this book, you’ll have gained the knowledge you need to enhance your C# and JavaScript skills and build full-stack, production-ready applications with ASP.NET 5 and React.
Table of Contents (21 chapters)
1
Section 1: Getting Started
4
Section 2: Building a Frontend with React and TypeScript
10
Section 3: Building an ASP.NET Backend
16
Section 4: Moving into Production

Answers

  1. In ASP.NET Core, the name of the file where we store any settings specific to the production environment is called appsettings.Production.json.
  2. The reason for our ASP.NET Core backend needing the Frontend setting is to set up the allowed origin in a CORS policy.
  3. We would use npm run build:qa to produce a QA build.
  4. If we didn't include the web.config file with our React frontend, we wouldn't be able to deep-link into our app—for example, putting the path to a question (such as https://qandafrontend.z19.web.core.windows.net/questions/1) directly in the browser's address bar and pressing Enter will result in a Page not found error being returned.
  5. Connection strings contain a secret username and password. It is safer to store these in Azure rather than in our source code.