Downloaded 45 times
![Maurice De Beijer [MVP], profile picture](https://cdn.slidesharecdn.com/profile-photo-mauricedb-48x48.jpg?cb=1756998088)
Uploaded byMaurice De Beijer [MVP]
Building great spa’s with angular js, asp.net mvc and webapi
This document discusses building single page applications (SPAs) using AngularJS, ASP.NET MVC, and ASP.NET WebAPI. It introduces AngularJS as a powerful JavaScript framework for building SPAs and CRUD applications. It notes that while AngularJS makes applications easy to build, large JavaScript apps can be hard to maintain. It then introduces ASP.NET WebAPI for building RESTful APIs and ASP.NET MVC as a server-side framework. It argues that combining AngularJS, WebAPI and MVC takes the best of both worlds, allowing structure from MVC while offloading UI tasks to AngularJS for performance. The document contains code demos of each technology and how they can work
Building great spa’s with angular js, asp.net mvc and webapi
- 1. Building great SPA’swith AngularJS, ASP.NET MVC and WebAPI
- 2. What are wegoing to talk about? • AngularJS • ASP.NET MVC • ASP.NET WebAPI • Single Page Applications 2
- 3. Who am I? •Maurice de Beijer • The Problem Solver • Microsoft Integration MVP • Freelance developer • DevelopMentor instructor • Twitter: @mauricedb • Blog: http://msmvps.com/blogs/TheProblemSolver/ • Web: http://www.TheProblemSolver.nl • E-mail: maurice.de.beijer@gmail.com 3
- 4. AngularJS • Powerful JavaScriptMVC framework • Makes it easy to build Single Page Applications • Focused on building CRUD applications • Very modular with Dependency Injection • Makes it relatively easy to build testable applications 4
- 5.
- 6. AngularJS cons • LargeJavaScript applications are hard to maintain • Even a browser based application needs a server part • Doing the same thing in every browser wastes CPU cycles 6
- 7.
- 8. ASP.NET WebAPI • Makesit easy to serve up data in a RESTful manner • Easy to consume from AngularJS – $resource – $http 8
- 9.
- 10. ASP.NET MVC • Powerfulserver side MVC framework – Routing – HTML helpers – Editor templates 10
- 11. ASP.NET MVC cons •Doing everything on the server is wasteful – UI lag because of latency – Need to worry about scaling sooner 11
- 12. Single Page Applications •SPA’s are great for the end user – Responsive • SPA’s are great for the server – Only request to the server when needed 12
- 13. Single Page Applicationscons • SPA’s can be hard to maintain – Less structure out of the box – Hard to maintain when large 13
- 14.
- 15. The best ofboth worlds • Mix ASP.NET with Angular – Use the structure of ASP.NET to create Mini SPAs – MVC HTML helpers to reduce markup repetition 15
- 16. The best ofboth worlds Demo 16
- 17.
- 18. 18 A big thankyou to our sponsors Gold Partners Silver & Track Partners Platinum Partners