Book Image

ASP.NET Core 2 and Vue.js

By : Stuart Ratcliffe
5 (1)
Book Image

ASP.NET Core 2 and Vue.js

5 (1)
By: Stuart Ratcliffe

Overview of this book

This book will walk you through the process of developing an e-commerce application from start to finish, utilizing an ASP.NET Core web API and Vue.js Single-Page Application (SPA) frontend. We will build the application using a featureslice approach, whereby in each chapter we will add the required frontend and backend changes to complete an entire feature. In the early chapters, we’ll keep things fairly simple to get you started, but by the end of the book, you’ll be utilizing some advanced concepts, such as server-side rendering and continuous integration and deployment. You will learn how to set up and configure a modern development environment for building ASP.NET Core web APIs and Vue.js SPA frontends.You will also learn about how ASP.NET Core differs from its predecessors, and how we can utilize those changes to our benefit. Finally, you will learn the fundamentals of building modern frontend applications using Vue.js, as well as some of the more advanced concepts, which can help make you more productive in your own applications in the future.
Table of Contents (15 chapters)

Continuous Integration and Continuous Deployment

In the previous chapter, we implemented one of the more complicated features of building a modern SPA frontend: server-side rendering. We had to make quite a lot of changes to the application to prepare it for SSR, as well as fix a number of bugs that cropped up when attempting to render browser-reliant components on the server. However, the application itself is now as feature-complete as it's going to be for the purposes of this book.

In this final chapter, we're going to improve our current deployment mechanism by implementing a Continuous Integration (CI) and Continuous Deployment (CD) pipeline using Visual Studio Team Services (VSTS). VSTS isn't the only option available to us, as there are many different ways that we can build a CI/CD pipeline, but as we're hosting within Azure, it makes a lot of sense...