John Papa

@Arnas:Good question. Those functions are defined below the return, but they are hoisted to the top since they are declared as a function declaration (e.g. a function without an explicit variable definition) .

@Obiwan007: I'm working on releasing the source for CC, but it may take some time. In the meantime, you can get it from a Pluralsight+ subscription

@Yazid: You can use services/factories to share data between controllers or you can use the eventing/broadcast features to send messages. Depends what you want to do.

You can place you HTML/CSS where you want, so no need for regions. Or use bootstrap or some layout from a source like wrapbootstrap.

Angular creates controllers per instance and services/factories as shared. Which is what you'd want for these. If you want to controller more, just create an object that you can do something custom with.

@alon: I have 2 courses on this now: Part 1 and Part 2  :)

@Yaz:You could think of AngularJS as a "prism"-like framework.

@dtyser4766: thanks , appreciate the feedback!

@zico: it is Toastr,  a library I wrote. https://github.com/CodeSeven/toastr. Also a NuGet package available.

@CAReed: At the beginning of all projects I first examine what the business needs and how the dev teams will support it. Then I try to much those against the technologies that are predominant. SPA works great when you want a Rich app, Reach across devices, Responsive UI (including reduce round trips(). All the R's.  If those dont matter, dont do it. If you need device integration, go app.

@dirq: Thanks! It will be a synopsis of much of the jump start course (highlights and super important parts). Plus I'll toss in some things I learned since then and a little more of the "why".

@olyjoe:Thanks!

@FJSmall:Yes, I will talk about why I chose what I did for this. I wont digress too much though as it may bore some I'l be happy to stick around after to dive deeper though. Or ask questions at the end ff my session.

@dirq: I don't use T4. I use breeze.js which helps take the models from the web service (JSON) and hydrate them into observable entities that Knockout uses. No duplication there.

SignalR rocks. Works great with KO.

web api and odata work great too, choose whatever web service tech you like.

folder structure is important, like always. using patterns like module pattern is critical, IMO. and dependency management is also super important (require.js with durandal or just angular).