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)

The easy way – Nuxt.js

Nuxt.js is a framework built on top of Vue.js, aimed specifically at the use case of building universal or server-rendered web applications. It makes it incredibly easy too, as it does a fantastic job of abstracting away the infrastructure code necessary to render on both the client and server. It leaves us to focus purely on building our application UI, and even provides a number of additional features that really help us do that. Things such as, but not limited to, additional component hooks for fetching asynchronous data, middleware, and shared component layouts are all included on top of the default functionality we get with plain Vue.js.

However, there is one downside, and unfortunately for us it's a major one. Nuxt.js has a dependency on being hosted directly within a Node.js server. It can't be directly linked with an ASP.NET Core...