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. An environment variable called CI needs to be set to true for Jest tests to work well in a CI environment.
  2. When we change the azure-pipelines.yml file, it is automatically committed and pushed to our master branch in our source code repository. The trigger option in the file specifies that a build should trigger when code is pushed to the master branch. So, a build is triggered when this happens.
  3. The -script task can be used to execute npm commands.
  4. The PublishBuildArtifacts@1 task can be used to publish artifacts to the pipeline.
  5. The frontend build sets an environment variable called REACT_APP_ENV, which the code uses to determine which environment it is in. This is the reason we have different frontend builds.
  6. The Azure App Service Deploy task type in a release pipeline stage can be used to deploy build artifacts to Azure App Service.