It is very important to know what process hosts your web application when it is running on IIS, as often you need to attach to that process, or troubleshoot issues related to process model.
However, Microsoft does not yet seem to have a diagram for ASP.NET Core, so I created my own,
If you recall Microsoft’s recommendation on setting up ASP.NET Core apps on IIS, you should immediately know the
- The application pool does not have ASP.NET configured, so the worker process
w3wp.exewill not load ASP.NET runtime.
web.configfile contains the settings of ASP.NET Core module, so
w3wp.exeloads the module and prepare the environment to host ASP.NET Core apps.
w3wp.exe does not execute any of your code, because it serves as the reverse proxy.
Incoming HTTP requests would be delegated to the actual Kestrel web server process, where the responses are generated.
- The process name would be
dotnet.exefor framework dependent deployment, while it would match your application name if you use self contained deployment.
- Kestrel process is not created if there is no incoming request. The creation when the first request comes might take a while based on the actual initialization it needs to perform.
- Kestrel web server can run on .NET Core or .NET Framework, based on your project configuration.
Note that ASP.NET Core on .NET Framework uses the same process model like ASP.NET Core on .NET Core, and that’s significantly different from ASP.NET 4.x.
If you want to attach a debugger to Kestrel web server process, sometimes you could not see the process, because ASP.NET Core module won’t initialize one if there is no incoming request.
The process model also applies to IIS Express.
When troubleshooting issues, you can always run Kestrel web server alone to see if the issue is within Kestrel or your own code.
Note that ASP.NET Core 2.x started to introduce the in-process hosting mode, which is similar to ASP.NET 4.x on IIS, which is not covered by this post. You can learn more about in-process hosting mode from this article.