Svcutil.exe MSBuild任务(Svcutil.exe MSBuild Task)

 在该示例中，他们注入$scope以便他们可以将其指定为弹出窗口选项中的scope属性。 
 
 也许如果我清理“控制器为”语法实际上是做什么的，你就不会觉得它太乱了:) 
 
 当您执行ng-controller="myController as ctrl" ，您所做的只是在该控制器的$scope上声明一个名为ctrl的变量，并将该值设置为该控制器的值。 将“myController作为ctrl”实际上与没有像这样的“as”快捷方式完全相同： 
 
<!-- markup -->
<div ng-controller="myController"></div>
 
 然后在你的控制器中： 
 
// controller
app.controller('myController', function ($scope) {
  $scope.ctrl = this;
});
 
 你将“myController作为ctrl”的唯一区别是$scope.ctrl = this只是在幕后发生的。 
 
 查看此演示 ，了解它们是同一个。 
 
 他们在您链接的演示中所做的事情在我看来完全没问题;） 
 
 如果您有兴趣，这是我写的关于“控制器为”的博客文章： http ： //codetunnel.io/angularjs-controller-as-or-scope/ 

In that example they inject $scope so they can assign it as the scope property in the popup show options.
 
Maybe if I clear up what the "controller as" syntax is actually doing, you won't feel like it's so messy :)
 
When you do ng-controller="myController as ctrl", all you're doing is declaring a variable called ctrl on the $scope for that controller and setting it's value to the this for that controller. Doing "myController as ctrl" is literally exactly the same as doing it without the "as" shortcut like this:
 
<!-- markup -->
<div ng-controller="myController"></div>
 
Then in your controller:
 
// controller
app.controller('myController', function ($scope) {
  $scope.ctrl = this;
});
 
The only difference when you do "myController as ctrl" is that $scope.ctrl = this just happens for you behind the scenes.
 
Check out this demo for proof that they are one and the same.
 
What they are doing in the demo you linked appears to be totally fine in my opinion ;)
 
Here's a blog post I wrote about "controller as" if you're interested: http://codetunnel.io/angularjs-controller-as-or-scope/