ASP.Net MVC verses WebAPI loading of initial Angular model

Question

I have finished a few MVC partial views which load their data using calls to a webapi Get method, to preload the data used by the angular controller.

This method works but it feels more logical to do this via the initial asp.net-MVC Partial view load via @Model for example. Rather than waiting for the page to load and angular to call the get method of my webservice i could have prepopulated the Model, but im not sure how this would pass the data to Angular using this method.

Answer 1

I have had the same issue (if one call this an issue) and ended up doing binding the model to the partial view at the server side. The main rational for the decision was that the model was already available at the time at the server side and I was not building a Single Page Application.

Had I been developing a SPA, I would store the partials as templates at the client side , then grab the model via WebAPI and do the binding

Answer 2

If you use AngularJS,then it's not need ASP.NET MVC. Just use web api for get data.I written a demo site for AngularJS+ASP.NET WEB API,hope to help you,this is the source code .

Answer 3

Does your web page have a lot of heavy client-side interaction or are you simply using Angular to initialize the data for your page on load?

If there's a lot of client-side interaction, you will probably want to keep using Angular. If not, you might want to go back to using MVC since your use case doesn't really require Angular.