In this segment, we will discuss containers. Containerization is another innovation that numerous ASP.NET engineers may not yet have a great deal of involvement with. Docker is the most well known containerization tool today. I’ll clarify how Docker functions at high level and why it’s a decent decision for deploying ASP.NET Core applications. When you set up a server or virtual machine to host your application, think about all the stuff that you need to do. Install dependencies like .NET and third-party libraries, configure things like IIS and NGINX, add environment variables and so on. If you have multiple servers, you have to do this setup manually on each one.
Thought to share new .Net Core 2.1 version features. Its announced now. And it has got some cool features. First of all to update the existing one, you need to have updated Visual Studio 2017 with 15.7 Preview 1 or newer. Once those updates, in place then you can install the utility directly from this page https://www.microsoft.com/net/download/dotnet-core/sdk-2.1.300-preview1.
Thought to share my latest project in collaboration with Chander Dhall. Chander and I started discussing on this project couple of months back and thought to collaborate in the project which is going to give more meaningful and professional product as an end result. Before talking anything about this book, I would like to put one disclaimer ahead of time. “This book doesn’t mean for freshers or for those computer professionals” . This I am saying because this book uses tons of client/server and many more sophisticated concepts which may appear overwhelming to freshers or to those just started programming. This book is all about how to marry all these technologies together and come out with a final industry standard product. Hence this book is meant for professionals who are good with basics at least. Having said that, now let me give glimpse of the book with complete first chapter.
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,
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
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.