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 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.
In this section, We will discuss about ASP.NET Core Hosting Model. The hosting model for ASP.NET Core is very different from previous versions. This is one of the key areas where majority of improvements happened in Core Model.
In this section, we are going to understand new pipeline concept in ASP.NET Core which is Middleware. If you have been doing ASP.NET stuff since a while, you must be knowing that HTTP-Handlers and HTTP-Modules have always been part of ASP.NET processing structure. But, with new ASP.NET Core concept, Handlers and Modules are now history. They are no longer in use. Rather than that new Pipeline is implemented and that is called Middleware. Developers can utilize normal existing Middlewares or they can write their own custom middleware depending on the need. Below is the high level diagram of MiddleWare.
In this section, thought of getting started new series on ASP.NET Core stuffs right from the beginning. The very first thing which needs to be done here downloading the core components from http://dot.net. Here, you will get two options LTS(Long Term Solution) and Current. I prefer LTS as this is how it is going to be in future. The major difference which I see is Project Type System (.xproj –> .csproj) change and project.json is going away. This has been done to embrace the existing Microsoft ecosystem which is based on .csproj system.
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.