Question

I have been thinking of doing some development with backbone.js javascript framework and i currently use ASP.NET MVC…

After considering this, it seems the ASP.NET MVC server side part would be redundant…

Backbone.js would contain my models which i would get by calling a REST service on my WCF machine.

My ui would be updated by Backbone / js …

Any logic would be in backbone.js controllers that is necessary to be executed on the client side.

I would really love some input, because i seemed to have arrived at the assumption that ASP.NET MVC is wiped out by backbone.js..

Anyboyd using both, why? and how?

Thanks in advance

Answer 1

Funny, I would have actually approached it the other way around: keep MVC instead of WCF. It does not matter if your MVC project will only server “data” rather than “views” to its clients MVC still provides a lot of the plumbing required for web applications.