Thoughts, tips, and tricks on software development. .NET | C# | Azure
14 January 2014
When a client requests a page in an ASP.NET MVC application, the HTML view is constructed in the server and then sent back to the client. The construction of the view includes, among other things, the initialization of control values.
With AngularJS, the process is different. The rendering is divided into two steps: the first step is getting the template from the server, and the second step is fetching the actual data.
When using AngularJS, some benefits of having strongly-typed views are lost. The first is that individual properties can no longer be bound to controls using the lambda syntax. The second is that now there needs to be more than one call to the server in order to render a full view.
One solution would be to declare the angular controller function in the same page as the view. Even though it would still not be possible to have the strongly-typed bindings, the angular controller would at least be able to use values from the model using razor syntax:
$scope.person = @Html.Encode(Json.Encode(Model))
The drawback of this approach is that the angular controller should be declared in the same page as the view.
Another option would be to use ng-init to initialize the client model:
<div ng-controller="MyCtrl" ng-init="person = @Json.Encode(Model)"> ... </div>
With this approach, the angular controller can be defined in an external file. The drawback is the reliance on the encoder. In some situations, a custom encoder might have to be used in order to get the desired result.