In this section, we are going to talk about dynamically importing modules and its related components. Say for instance, your CORE SPA is hosted on one server. And different teams are basically building different features as modules, which needs to be injected as part dependency injection. Idea is keeping Core part leaner and meaner. Then how could we achieve the same. In the last post, we have seen similar kind of post, where in we injected modules dynamically but, module was known at compile time as we have used webpack’s import which basically takes path to module as input parameter. In this case, module’s can be injected by reading some kind of metadata coming from somewhere. Hence, you can have get some JSON files with some metadata say what modules’ and related dependencies to load. Then, it will load accordingly
In this section, we are going to see, how to dynamically import modules and other related components. In enterprise apps, there might be a scenario, where in you end up loading the modules based on some metadata, say which is coming from some REST call may be. In those scenarios, this kind of implementation is needed. We will discuss Lazy Loading in detail when we talk about those scenarios. However, let’s look at the code where we lazy load modules with all its dependencies.
In this section, we are going to continue from the last section and will get started with Child Routes aka Nested Routes. Nested routes is the concept of containing routes within other routes. With nested routes we’re able to encapsulate the functionality of parent routes and have that functionality apply to the child routes. This is one of the nice ways to isolate different functional areas. Otherwise, imagine your base routes will grow like anything. I have configured the routes in such a way that all reviews now sit under location. Below, I have pasted modified structure of app.
In this section, we will continue from last post http://bit.ly/ng4-route-1, where we have introduced routing. In that post, although routes were working but there was no visual indication for the same. This is a simple change, basically CSS change. Let’s fix that first. Below is the snippet for the same.
In this section, thought to share one of the projects, which I was trying using MEAN stack. Its a very simple project. Basically, its a dumping ground of messages with complete CRUD functionality with Authentication/Authorization via JWTs bearer token. Now, in this MEAN stack, A –> Angular 4, which is nice here. This is how application looks
Thought to share one more view with ASP.NET Core hosting as Windows Service. Now, here is the catch. If you have already decided, that you would like to host ASP.NET Core as Windows Hosting, then you probably pick the ASP.NET Core Template on top of .NET Framework as this will only give Windows’ Hosting library references. If you pick this template, then half battle is already over. Then, in that case, you can simply focus on windows service.