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)

Setting up and configuring SSR

We've finished all of the refactoring that we needed to do in order to prepare the application to be rendered on the server. We now need to look at how we configure our application to be booted on both the client and the server, as we already determined that we need to be very specific about what happens when and where. This also includes enhancing our existing webpack configuration so that it too understands how our application needs to work on both the client and server.

Let's start with how we actually boot our application. Currently, we have a single ClientApp/boot.js file, which handles this task for us nicely as we only ever boot the application on the client. However, we now need to split this file into three separate parts: app.js, client.js, and server.js. As you've probably already guessed, client.js and server.js are used...