cihanduruer

Uh Oh, my bad. I pushed the remaining files. So if you look to repository you'll see the views. Yes i have a views folder.

Sorry for inconvenience.

You catch a good spot, thanks ! In future i will create multiple controllers, sure depends with the logical concern.

I will read read style guide and ng-annotate.

Unit testing is crucial you are right. I need to add to seed project.

By the way what do you think about this article ? http://www.wintellect.com/blogs/jlane/five-reasons-asp.net-d...

We can say fashion and learning. Code doesn't contain any logic.

TS is only way of writing JavaScript. Which doesn't affect on architecture.

So I would like to hear your comment about, can i use this project as a seed project for my future projects ?

First of all, thanks for your time.

I would like to build a single page application for one of my customer. Application is not very complex (nothing like a financial or manufacturing applications). It will be public application and possible traffic/load is completely unknown.

I choose that stack because of fashion. I would like to learn another way to develop. I am quite happy with my existing stack. If i use my stack, project can be also scale-able and asynchronous enough to create modern app.

My plan is also continue with the hybrid stack, so back-end is going to be a REST Api with ASP.Net Web Api secured with OWIN/Katana. I am planning to use new stack only for presentation layer so far.

I slightly disagree your find an existing framework and continue approach. Because in my opinion if i code everything i will learn more(i know with pain). Choosing framework/package will also take tremendous time for beginner of the stack.

Do you think learning a new stack because of a fashion is valid reason ?