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.
In the last section, we have discussed, how to host application using HTTP.SYS. Now, in this section, we will address how to handle CORS issue with ASP.NET Core APP hosted using Http.Sys and Angular 4. With current setting shown below,
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