Skip to main content

Dotnet Core Application Hosting And Debugging Using Local IIS Server


Dotnet core application can run by using hosting servers like
1. IIS EXPRESS(built-in  server in visual studio)
and so on many other servers.

The most commonly used server at development time is IIS EXPRESS. But we can do debugging the application by hosting it on Local IIS Server also. Using Local IIS helps to test any server-level configuration locally before going to the production server.

About Platform:

The platform using for this sample below
1. IIS Server 7 or above,
2. Dotnet Core Framework 2.2v+
3. Dotnet Core MVC
4. Visual Studio 2017 or above (editor)

Getting Started: 

Now we are going host a sample ASP.NET Core MVC application in our local IIS Server and then we are going debug our application in visual studio using Local IIS Server.

Download And Install DOTNET Core SDK And Runtime:

Go to the Microsft Dotnet Core downloads and download and install dotnet core SDK and Runtime.
SDK is the Software Development Kit, provides libraries to develop ASP.NET Core Applications and Runtime used by hosting servers.

Verify AspNetCoreModuleV2 Installation:

Now opens your local IIS server, goto Sites => Default Web Site select it. On the right side, pannel go to IIS => Modules select

"AspNetCoreModuleV2" displays, it says we successfully install Dotnet core 2.2  runtimes. If your not able to see that module once restart your pc and check.

Create ASP.NET Core MVC Application:

Now create core MVC application. Click here create MVC project

Creating And Configuring Web.config:

By default in the dotnet core web application, we don't get web.config. Add web.config file as follows
<?xml version="1.0" encoding="utf-8"?>

  <!-- To customize the core module uncomment and edit the following section. 
  For more info see -->
      <remove name="aspNetCore"/>
      <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified"/>
    <aspNetCore processPath="dotnet" arguments=".\bin\Debug\netcoreapp3.0\IISHostingTest.MVC.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />

  • 'AspNetCoreModuleV2' specifying the server needs to target the Dotnet Core Runtime version 2.2 plus. So in the config section, we specified explicitly to run on 'AspNetCoreModuleV2'.
  • Now observe the 'aspNetCore' XML tag, its attributes are commands to startup the application. We need to pass  'arguments' value ".\bin\Debug\netcoreapp2.2\your_mvc_application_name.dll"(specifying our startup project dll location)
  • 'stdoutLogEnabled' gives access to log the application level errors at the path provided in 'stdoutLogFile'.

Configure Application And Domain Binding:

Now open the IIS server. Goto Sies => Add WebSite opens a popup as shown below

  • SiteName => CoreApp (hosted application name in IIS Server)
  • PhysicalPath => "D:\exmples\AspCoreWithLocalIISSetup\LocalIISSetupSample\LocalIISSetupSample"(my sample Path)
  • HostName => "corewithlocaliis" (your site name, adding to the iis server)

Domain Binding In Host File:

Now we need to register our domain like "corewithlocaliis" in the local host file. Now got to "C:\Windows\System32\drivers\etc" open local host file and add "      corewithlocaliis" in that file.

Test Application:

Now search your domain "corewithlocaliis" in browser your able to see the output as below

now we successfully configured our application, local IIS.

Visual Studio Build Issue (Could Not Copy DLL Files):

Now while accessing the application from IIS, change code in visual studio and build project we get the following build issue.

This issue because while DLL files are used by IIS, the visual studio tries to delete existing DLLs to recreate them on build command.

Resolve Build Issue:

In your application now add file name a "app_offline.htm" (note: don't use .html) in wwwroot folder. Now click on edit option on yourapplication_name.cproj add the following code.

  • Target => Name => PreBuild means this tag gets run before building the project. Inside it, we are copying the "app_offline.htm" file from the wwwroot folder to the main folder. After copied the "app_offline.htm" file, IIS goes offline until the file deleted. Now build starts since IIS in offline mode build will get success.
  • Target => Name => PostBuild means this tag gets run after building the project. Inside it, we are deleting "app_offline.htm" from the root folder, so that the IIS server gets active.
  • If we carefully observe this only executes in debug mode nothing but development time. In release mode, there won't any effect of the tags in the image above.
  • Now build the project build issue fixed.
Note Click here to copy the event tags

Debugging Using 'dotnet.exe' Command:

Now go to visual studio, select break pointer to debug code. Now click "Ctrl+Alt+p" opens Attach to process popup as below

Select the donet.exe process, so the debugger gets activated. That's it we are good to debug our dotnet core application with our local IIS server.

SetUp OverView:


Asp.Net Core Sample application has been created, hosted in local IIS Server and debugging the project from Visual Studio. Discussed about pre and post build events helps in creating and deleting app_offline.htm file. Discussed Web.config configurations.


Popular posts from this blog

Blazor WebAssembly Custom Authentication From Scratch

In this article, we are going to explore and implement custom authentication from the scratch. In this sample, we will use JWT authentication for user authentication. Main Building Blocks Of Blazor WebAssembly Authentication: The core concepts of blazor webassembly authentication are: AuthenticationStateProvider Service AuthorizeView Component Task<AuthenticationState> Cascading Property CascadingAuthenticationState Component AuthorizeRouteView Component AuthenticationStateProvider Service - this provider holds the authentication information about the login user. The 'GetAuthenticationStateAsync()' method in the Authentication state provider returns user AuthenticationState. The 'NotifyAuthenticationStateChaged()' to notify the latest user information within the components which using this AuthenticationStateProvider. AuthorizeView Component - displays different content depending on the user authorization state. This component uses the AuthenticationStateProvider

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server. Main Response Caching Headers are like below Cache-Control Pragma Vary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response. private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores. max-age - this directive represents a time to hold a response in the cache. no-cache - this directive represents no storing of response and always fetch the fr

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route. An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaul

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library  jQuery Validate . In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples. Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio. Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as bel

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload: The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client.  Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file.  Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk.  If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application. Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.   Check the link to use the Visual Studio Code for .NET Core Application . IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files f

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items. The main building block of ion-picker as follows: PickerController PickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker. Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger&quo

.Net Core HttpClient JSON Extension Methods Using System.Net.Http.Json Package

.Net Core 3.0 onwards Microsoft brought up a new package called System.Net.Http.Json. This new package provides JSON extension methods for HttpClient. These JSON extension methods will have a prebuild mechanism for serializing or deserializing response data or payload of HttpClient call. System.Net.Http.Json extension methods that are provided to HttpClient, few of them are mentioned below. GetFromJsonAsync PostAsJsonAsync PutAsJsonAsync ReadFromJsonAsync In this article, we understand System.Net.Http.Json package by implementing the HttpClient samples by with and without JSON extension methods and compare them. Create A .Net Core Web API Sample Application: Let's create a .Net Core sample Web API application, from this application we will consume another Web API by implementing HttpClient calls. We can create a Web API sample application using IDE like Visual Studio 2019(Supports .Net Core 3.0 plus) or  Visual Studio Code . Create A Typed Client: In .Net Core using the Http

GraphQL API Integration In Asp.Net Core Application

Introduction: GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data. How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions. HTTP-POST is the only Http verb recommended by the GraphQL. The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API: The main building blocks of GraphQL API is Schemas and Types.  A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc. T

ASP.NET Core Web API Versioning

Introduction: An iteration and evolutionary changes of an ASP.NET Core Web API is handled by Versioning. Versioning of an API gives confidence to the clients which consumes API for a long time. Any changes or development of an API will be accessible using the new version and it won't cause issues to the clients consuming the old version of API. When To Use Versioning: Any API response changes. Developing an API by implementing testing levels like 'Alpha', 'Beta', and 'RC' versions before releasing Production. Deprecating an API which means API going to be removed or upgraded by a version within a short period. Versioning Types: Query String Versioning Url Path Versioning Media Type Versioning API Version Nuget: To Configure versioning to AspNet Core Web API Microsoft provided a library(Microsoft.AspNetCore.Mvc.Versioning). So to use the versioning library please install NuGet below.              Install-Package Microsoft.A

Blazor Server CRUD Operations

Introduction: Blazor Server is a web framework to develop server-side single-page applications. Blazor is made up of components with the combinations on C#, Html, CSS.  Blazor Server is production-ready from the .Net Core 3.0.  Blazor Server Working Mechanism: Blazor Server is a very light-weight web development framework.  In Blazor Server, not all code gets downloaded to the client browsers. Blazor Server made of components these components can be a block of code or page with respective navigation.  Blazor server application communicates with the server with a SignalR background connection which is inbuilt functionality. Application click,  form submission, change events, application page navigation every operation is carried out by the SignalR connection by communicating with the server.  Blazor updates the Html DOM very gently on every data update without any overhead. Blazor Server application maintains a nice intelligent tree structure to update the required inform