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

Questions

Check whether all of that information about forms has stuck by answering the following questions:

  1. What property on an uncontrolled input element can be used to set its initial value?
  2. The following JSX is a controlled input element:
    <input
      id="firstName"
      value={firstName}
    />

    However, users are unable to enter characters in the input. What is the problem here?

  3. When we implement a form field as follows, why do we tie label to input using the htmlFor attribute?
    <label htmlFor="title">{label}</label>
    <input id="title" … />
  4. What object in React Hook Form allows us to access validation errors?
  5. What can we use from React Hook Form to determine whether the form is being submitted?
  6. Why don't we use the isSubmitted flag with formState to determine whether a form has been successfully submitted?