In this section, we will talk about another way, via which we can inherit prototypes. Here, I’ll be using Object.Create to use the same. In the last section, we have seen function constructor pattern to create objects from the blueprint. With that object.create() method, things work bit differently. In this case, we first define an object which will act as a prototype and then create a new object based on that very prototype.
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.
Thought to share new additions around dotnet cmd. I guess with these additions, this may be the perfect timing for building SPA (Single Page APP) with ASP.NET Core as backend and any of the below listed libraries as Front-end choice.
Recently, I came across a project which is actually written in silverlight which means basically its a desktop app. However, there is web version of that as well there where in it works with Kendo+Jquery combination. Since, its JQuery, hence every developer has got their own way of implementation which is a pain in maintaining and scaling the project. I discussed with my team and thought of writing the same in such a way that still the existing stack will be working and side by side; I will be pushing the same on Angular 4. Kind of monumental task as this is not greenfield project where I have the choice to choose tools of my choice.
In this section, I thought of talking of sharing little tip around service registration. Here, I’ll be explaining the same using Repository Pattern in ASP.NET Core. Dependency Injection is first class citizen here which means DI is one of the key features of ASP.NET Core. With that being said it is not at all required to rely on any third party containers. It is optional. Same can be achieved in startup configuration as shown below. But before that let’s understand different types of service registration.
Thought to share one of the errors which I usually face, whenever I switch machine. Scenario is I am working on any greenfield project which is basically an angular 4 project with asp.net core. I have a habit of keeping my code on source control which is git in this case. However, when I clone the same on different machine and install my usual dependencies with npm install; soon after that when I run my app, it gives me below error.
After speaking internationally in US, Canada, Sweden, Norway, Netherlands, UK, Belgium, Germany and many other countries, Microsoft MVP, ASP.NET Insider, Web API Advisor, Azure Insider – Chander Dhall is coming to India.
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, we will see execution timing of directive controller and associated link function in action. I’m looking at the timing of directive’s controller and link functions. As the DOM is compiled by AngularJS, the directive controller and link function execute at different levels of the compile lifecycle. When AngularJS compiles the DOM, it walks down the DOM tree in a.