I'm not an expert in these building blocks, but at first glance it seems to me:
ASPNET MVC wants to generate the views and manage the models for an app on the server side. It views the browser as a somewhat dumb presentation engine, a consumer of the views that are provided for it by the server.
backbone.js would like to generate the views and manage the models in the browser. It views the server-side as a fairly dumb REST-based persistence engine.
This seems like a simplistic view. I'm sure it's not the whole story.
What are the real opportunities for integrating these two things? Does it make sense to do it? Or is there too much overlap between them for it to make sense?
I like to see some analysis or discussion of this, if anyone can refer me.