Thought to share one small application built with Angular 4 CLI. Here, I was checking few Apple APIs. And then realized, since its a public API, hence something can be built around that using Angular 4. Therefore, built a little Angular App using that.
In this post, we are going to discuss how to host ASP.NET Core app using HTTP.Sys aka web-listener. HTTP.sys is useful for deployments where you need to expose the server directly to the Internet without using IIS.
In this section, we will talk about about handling CORS issue with ASP.NET CORE and Angular 4 application. As part of Authentication, this app uses Windows Authentication. I have created app using ASP.NET Core 2 Angular template and then using the application. Application structure looks like
In this section, we will learn more about service injection. Before doing so, let’s create a new service. In the last section, we have understood different stages of ng-hooks. Now, if you have read that post closely, you would have observed one pattern that, I logged messages more often just to prove the point. This is quite repetitive. Therefore, these are the places where services fits in nicely. Main role of any service is to simplify the things. Here, you can think of one dedicated component doing the job. Hence, without wasting time, let’s get started.
In this section, we will talk about Angular Life Cycle hooks. Angular supports couple of life cycle hooks. Let’s take a closer look at that. In a nutshell, whenever any new component gets created, Angular goes to couple of different phases in this creation process. This also gives us opportunity to hook into different phases and utilize the same to its maximum. Below is the glimpse of ng-hooks in sequential order.
In this section, we will talk about template reference. Now, in the Movies.Component.html file, we are already using ngModel and that is fine as we can get data via this way as well. Local reference is the way to get any HTML template access. Now, this variable will hold reference to this HTML element.
In this section, we will continue from the last section, where we have seen Event Binding via @Output decorator. Like @Input decorator, we can also assign alias to @Output decorators like shown below. In that case, you need to listen to this alias as well.
In this section, we will extend our existing example to new level. Many a times it happen, that InputType, which we are referring, we don’t want to use the same property outside the component. Therefore, in that case, we may use alias for @Input() types.
In this section, we will get started with simple angular components and then we will isolate the structure into different components and then try to communicate between the components. For this post, readers are expected to have basic working knowledge of Angular 2/4 and how to scaffold projects with Angular CLI. With that being said let’s get started. Below, I have created simple angular 4 project via CLI.