As shown in Project Silk (Microsoft P&P) Modularity is very important in SPA as an Project grows larger an many people are working on it.
An example for this is to structure your SPA with CommonJS Modules oder require.js.
How can this be done in an SPA with knockout etc.?
How should the modules communicate with each other? (Pub/Sub, Eventing etc?)
Who manages different modules that are tied to different logical pages in the (technical) SINGLE Page?107 votes
Prescriptive guidance is in the works for the next version of the web tools. There will likely be project templates, snippets, item templates etc. for proper modularize Angular/KO/Ember/etc. apps. Point is, this is being actively looked into right now
Would be good if the SPA template could support AngularJS as well as KnockoutJS. Or perhaps a separate template makes more sense.56 votes
At our RTM in a month or so we will have Knockout, Breeze, and Ember. We are looking at providing other as well and we have extensibility so more can be added by third parties.
SPA templates released in WebTools 2012.2 are very primitive or based on WebAPI. It would be nice to know:
1. How can we write SPA that use Durandal and Mvc/Razor together (with optimization)?
2. How to manage with validation on client-side. You should provide ability to generate client-side validation like in MVC.
3. How to restrict access to specified views like in traditional web applications.
4. Both SPA and HotTowel templates are CRUD application. Provide sample that are more Task based UI.35 votes
We’re planning much deeper client-side framework integration in a future version of Visual Studio and ASP.NET.