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

API versioning

So what we are going to learn about in this section is a few things about versioning ASP.NET Core Web API. We will start by talking about what API versioning is and some versioning strategies in APIs, then we will dive into some code and integrate API versioning with OpenAPI so you can see the versioned APIs in your Swagger UI.

Now let's start by defining API versioning.

What is API versioning?

In a nutshell, API versioning is how you want to deal with API changes over time. Most of us backend developers concentrate on building and deploying a web service because that is our job. They're usually the written tasks that we have to implement in a typical project. But sometimes we forget that we're going to have to support the web service for the next 5 to 10 years, or the developers replacing us will.

Once the web service is deployed and developers have coded against the API, there will be users who are relying on the APIs that we have built....