ASP.NET MVC + Backbone.js, does this make sense? Is ASP.NET MVC Really Necessary?

Question

I was thinking of doing some development using the javascript structure of backbone.js, and I'm currently using ASP.NET MVC ...

After considering this issue, it seems that part of the ASP.NET MVC server will be redundant ...

Backbone.js will contain my models, which I would get by calling the REST service on my WCF computer.

My ui will be updated using Backbone / js ...

Any logic will be in the backbone.js controllers that need to be executed on the client side.

I would really like the input because I seem to have come to the assumption that ASP.NET MVC is destroyed by backbone.js ..

Anyboyd uses both, why? And How?

Thanks in advance

Answer 1

Funny, I would actually approach it the other way around: save MVC instead of WCF. It doesn’t matter if your MVC project is just server data, not "views" for its clients. MVC still provides most of the plumbing required for web applications.

Answer 2

I would really like the input because I seem to have come to the assumption that ASP.NET MVC is destroyed by backbone.js ..

No. the host is running on the client.

There is a difference between what can be done on the client and server.

, REST.

, , .

.

#/.NET/Massive. .

" ", .

, javascript , , node.js, / . .

Answer 3

,

My short MVC answer absolutely does not disappear when using client frameworks. MVC is more than recording views in Razor. You get model binding, authentication, authentication, and the ability to manage your URL structure by choosing controllers, actions, and routes. 80% of the utility is useful even without using server views.