Shulou(Shulou.com)06/01 Report--

This article mainly introduces the example analysis of IIS storage configuration area file ApplicationHost.config, which is very detailed and has certain reference value. Friends who are interested must finish reading it!

For a newly created website, take ASP.NET MVC5 as an example.

We do not configure some handlers or modules in the configuration file (web.config) of the web page, such as the SessionStateModule module that handles Session, the UrlRoutingModule module that maps Url, and so on.

But we can still access Session normally in the controller. The url we requested is still correctly mapped to the controller and Action.

This is because many modules are registered in the modules element of ApplicationHost.config in the configuration file of IIS, which are used by all applications hosted by IIS.

Modules registered in the ApplicationHost.config file have global scope because they are registered for all Web applications hosted by IIS.

Similarly, native code modules defined in the globalModules element of the ApplicationHost.config file also have global scope. If the Web application does not require a global module, you can disable it.

Of course, this is only a small part of the function of this configuration file, and sometimes the mapping relationships we add in the IIS manager are also stored in this configuration file.

But without full assurance, do not modify this configuration file or back up before making changes. Because this file is used by all applications hosted by the entire IIS. The loss of some obscure configuration nodes can be fatal for some programs.

Below we list some of the contents of this configuration file, you can also search this file on your own computer C disk and check the contents in detail.

The configuration nodes above are all native code modules (native-code). If you want to add your own managed code module (managed-code), add it to the early modules.

These files are then read through environment variables. They are the cornerstone of the whole iis.

In the configuration node above, both native code module (native-code) and managed code module (managed-code) are listed.

As you can see above, the configuration information such as the modules we see in the iis manager comes from here, including the handler mapping below. Click on the handler mapping in iis, which shows the official configuration file of the handler.

The above handler is configured by default by iis, and you can see that in order to run in a variety of environments (including different .net framework versions and different cpu versions), take processing * .aspx as an example to analyze this setting.

In integrated mode, only the runtime version is distinguished, because managed code is compiled into an intermediate language, which, when used, is compiled into native code (nativa-code) based on the cpu model of the running machine. So there is no need for a configuration like bitness64.

In classic mode, asp.net is only an extension of ISAPI of iis, and different Framework versions and runtime versions have compiled specific aspnet_isapi.dll, so you only need to choose the corresponding dll according to the specific running machine.

The files in the iis configuration store are used by the entire iis-supported application, adapting to different local environments, without full assurance and understanding, try not to modify this file.

The above is all the contents of the article "sample Analysis of IIS Storage configuration area File ApplicationHost.config". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.