Book Image

ASP.NET Core and Vue.js

By : Devlin Basilan Duldulao
Book Image

ASP.NET Core and Vue.js

By: Devlin Basilan Duldulao

Overview of this book

Vue.js 3 is faster and smaller than the previous version, and TypeScript’s full support out of the box makes it a more maintainable and easier-to-use version of Vue.js. Then, there's ASP.NET Core 5, which is the fastest .NET web framework today. Together, Vue.js for the frontend and ASP.NET Core 5 for the backend make a powerful combination. This book follows a hands-on approach to implementing practical methodologies for building robust applications using ASP.NET Core 5 and Vue.js 3. The topics here are not deep dive and the book is intended for busy .NET developers who have limited time and want a quick implementation of a clean architecture with popular libraries. You’ll start by setting up your web app’s backend, guided by clean architecture, command query responsibility segregation (CQRS), mediator pattern, and Entity Framework Core 5. The book then shows you how to build the frontend application using best practices, state management with Vuex, Vuetify UI component libraries, Vuelidate for input validations, lazy loading with Vue Router, and JWT authentication. Later, you’ll focus on testing and deployment. All the tutorials in this book support Windows 10, macOS, and Linux users. By the end of this book, you’ll be able to build an enterprise full-stack web app, use the most common npm packages for Vue.js and NuGet packages for ASP.NET Core, and deploy Vue.js and ASP.NET Core to Azure App Service using GitHub Actions.
Table of Contents (25 chapters)
1
Section 1: Getting Started
4
Section 2: Backend Development
13
Section 3: Frontend Development
20
Section 4: Testing and Deployment

Introducing Cross-Origin Resource Sharing or CORS

Before we discuss CORS policy and cross-origin resource sharing, try to send a POST request to version 2 of the WeatherForecast endpoint. See if you can still retrieve some of the JSON response of the WeatherForecast controller using Postman as shown in the following screenshot:

Figure 13.6 – Sending a POST request to WeatherForecast using Postman

Figure 13.6 means that the endpoint is still working correctly, but it would not work in another SPA.

I created a React application that runs on port 3000 to see if it can fetch the JSON objects from the WeatherForecast controller. No auth is required in the request, but the React application logs errors in the console; see Figure 13.7:

Figure 13.7 – Blocked by CORS policy

The error in Figure 13.7 says that access to XMLHttpRequest at the endpoint from localhost:3000 has been blocked by CORS policy. The No Access-Control-Allow...