Single Page Architectures with VueJS and ASP.NET Core
summary
Shows a working pattern: a Vue CLI front end and a separate ASP.NET Core API are two projects, proxied in development via spa services extension so one URL serves both and avoids CORS; production copies the Vue build into wwwroot with NPM run build. Uses Axios for HTTP, Vuex for centralized state (actions → mutations → state), router lazy loading to keep bundles small, and cookie or JWT auth (JWT needs custom refresh/revoke). The setup compiles, runs, and upgrades if the CLI is not ejected.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:22Evolution of web development
- 4:25Why choose Vue.js
- 6:11Architecture overview
- 8:54SPA fundamentals
- 11:50Vue components
- 14:13CLI tools and config
- 18:06Setting up the projects
- 22:15Vue routing
- 26:22Lazy loading routes
- 29:52Development workflow
- 32:37Proxying in development
- 37:18Production deployment
- 39:41Data access with Axios
- 42:46State management with Vuex
- 54:41Authentication and security
- 59:26Conclusion and resources
related talks
57mWorking with Vue 3.0 and ASP.NET Minimal API
01h 01mWorking with Vue 3.0 and ASP.NET Minimal API
36mLaravel and Vue JS
22mWays to architecture your vue/nuxt app
04mNuxt.js: Universal Vue.js Applications
23mFull Stack Vue in the Era of Serverless Computing
29mWho Are Vue? Authn In Vue, The Important Parts
26mBe Lazy, Be Smart, Be Nuxt.