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. The HomePage component will be rendered when the browser location is /, and the SearchPage component will be rendered when the browser location is /search.
  2. To enable a path of /login to render the sign-in page, we can define an additional Route component as follows:
    <Route path="signin" element={<SignInPage />} />
    <Route path="login" element={<SignInPage />} />
  3. The NotFoundPage component will be rendered.
  4. We can reference the userId route parameter using the useParams hook as follows:
    const { userId } = useParams();
  5. We can reference the id query parameter using the useSearchParams hook as follows:
    const [searchParams] = useSearchParams();
    const id = searchParams.get('id');
  6. The Link component can be used so that navigation only happens on the client:
    <Link to="products">Products</Link>
  7. In order to programmatically navigate, we first need to get a function from the useNavigate...