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)

Summary

Azure may not be the cheapest option when deploying small personal projects to the cloud, but for businesses with many different applications, it's highly competitive in comparison with the other major cloud hosting providers. We've only scratched the surface of what you can do with the Azure portal, so I strongly encourage you to make the most of the free 30-day trial and make use of as many different resources as you can.

We started out by getting to grips with the concepts of Azure subscriptions, resources, and resource groups. Once familiar with those, we started to deploy the resources we needed for our application, including a single resource group, a database server, a SQL database, an app service plan, and an app service. We then made some changes to the application itself in order to prepare it for deployment into Azure. The main change we needed to...