Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying ASP.NET Core 2 and Vue.js
  • Table Of Contents Toc
  • Feedback & Rating feedback
ASP.NET Core 2 and Vue.js

ASP.NET Core 2 and Vue.js

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

Enabling CD

Similar to when we initially created the build definition, as it stands, the release will only run when we trigger it manually. This may be what you want, depending on the preferences of you or your business, but if you'd rather have your releases triggered automatically after every successful build, then we need to enable CD.

To do so, head back to the Pipeline tab of our release definition, where you'll see a lightning bolt button in the Artifacts section. This will open another modal from the right of the screen, where you can set the Continuous deployment trigger:

Flip the switch here to Enabled, then remember to hit the Save button again to ensure that these changes are persisted. Now, every push to our master Git branch will trigger a new build, which if successful will in turn trigger a release to our production Azure environment.

...

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

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY