Hosted Web Core API Reference
This section describes the functions that developers can use to host Web pages with the Hosted Web Core. Hosted Web Core enables processes other than a worker process to load an instance of the IIS core. This instance requires a separate configuration file and can host only one application pool.
In This Section
|PFN_WEB_CORE_ SET_METADATA_DLL_ENTRY||Starts an instance of the Hosted Web Core.|
|PFN_WEB_CORE_SET_METADATA_DLL_ENTRY||Sets metadata options for a web core activation.|
|PFN_WEB_CORE_SHUTDOWN||Shuts down an instance of the Hosted Web Core.|
Creating an instance of the Hosted Web Core enables a process other than a worker process to load the IIS core, which is the base Web application and content-serving functionality that is provided by IIS.
Applications written using the Hosted Web Core do not inherit the monitoring functionality that is provided by the Windows Process Activation Service (WAS) for IIS applications.
Hosted Web Core enables a process to host Web pages without having to re-create the application functionality that is provided natively by the IIS core. For example, the IIS core already provides authentication and authorization; therefore, a developer who is writing an application that uses the Hosted Web Core would not have to manually create a security infrastructure. The IIS core also provides additional functionality that would require a lot of effort to manually re-create, such as Internet Server API (ISAPI) filter and extension support, functionality provided by the HTTP protocol stack (HTTP.sys) driver, authentication, and so on.
The Hosted Web Core requires a configuration file that follows the design of the ApplicationHost.config file, except that Hosted Web Core supports only one application pool. For more information about the configuration file required for Hosted Web Code, see Walkthrough: Creating a Configuration File for Hosted Web Core.