Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • ASP.NET Core 2 and Vue.js
  • Toc
  • feedback
ASP.NET Core 2 and Vue.js

ASP.NET Core 2 and Vue.js

By : Ratcliffe
4 (8)
close
ASP.NET Core 2 and Vue.js

ASP.NET Core 2 and Vue.js

4 (8)
By: 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)
close

Displaying a list of products

As we'll be building a full e-commerce application, it makes sense to start things off with a list of fictional products that we are going to sell. We'll keep things simple to start with and keep this component contained within our home page before we introduce the additional complexity of multiple pages.

When first starting out with Vue, it is very easy to just keep dropping all of our components in the ClientApp/components folder. However, it will soon get very difficult to find what we're looking for once we have more than a handful of components to maintain. Instead, I tend to group my components by page or feature, with a folder for each inside the components directory. It doesn't really matter what we name these features, as long as it's obvious to us which components belong to each one.

Create a ClientApp/components...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete