Angular and ASP.NET MVC hybrid application

When I first started looking at Angular it was still called AngularJS.  Then came Angular2 and Typescript.  At the same time, Microsoft was busy turning over all the boxes of .NET leading to utter chaos. As is the case in application development every few years, new and disruptive technology comes along that requires investments of time to learn.  When I started using Angular, it has been in the context of being delivered via an ASP.NET application.  This complicates things even further, since with MVC, there is routing involved and its own application life-cycle.  Then there are the Angular module loaders.  With .NET core, things get a little more streamlined with less work-arounds.  If you're still using MVC5 or earlier, I found it easier to use System.js as opposed to the other popular loader known as webpack.  Here is a good example of using Angular within an ASP.NET MVC (not .NET core) application

http://hive.rinoy.in/angular4-and-asp-net-mvc-hybrid-application/