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.
In this post, I thought of addressing one of the errors which many of friends have been asking since few days. Actually, angular template under dotnet stack has been changed. For more info around the same, please refer my earlier post http://myview.rahulnivi.net/dotnet-angular-aurelia-knockout-react-redux-vue/. It means developers when used to execute angular template either via dotnet cli command or via yeoman generator, there used to be app.module.ts file. At this moment, when I try creating new component say ng g c movies, this will give below error.
In this section, I thought of talking a question that I’m frequently asked, “should I invest time in Angular 1 or 2 (now angular 4)?”. I hope this post enable to take decision wisely and effectively. Whenever, I’m asked this question, I counter questions developers with my questions.
In this section, I will talk about my new Yeoman generator. In this Yeoman Generator, I have published ASP.NET Core scaffolding template with Angular 2 and TypeScript. This will enable developers to get started with Single Page App (SPA) development quickly. One point to note here is, this template is align with new ASP.NET Core changes where it embraces .csproj system rather than .xproj.