Creating Hosted Web Core Applications
This section describes how to design a Hosted Web Core. The topics in this section demonstrate how to create an application that uses the Hosted Web Core features, and how to create a custom configuration file for your application.
Hosted Web Core enables developers to create applications that load the core IIS functionality. Applications that load the Hosted Web Core use a separate configuration file from IIS, and this feature enables software developers to customize the functionality for their applications. For example, you can write an application that uses the Hosted Web Core functionality to serve Web pages and applications from a Web site that is separate from the Web sites that are hosted by IIS on the same server. When the World Wide Web Publishing Service (WWW service) for IIS is recycled, your application will continue to serve Web pages to Web clients.
Hosted Web Core applications do not inherit any of the reliability and monitoring features of IIS. Developers that use the Hosted Web Core features to create applications must provide any recovery and performance-related functionality. Because Hosted Web Core applications can host only a single application pool, they are generally single-purpose applications.
For most situations where customized functionality is required, developers should consider creating HTTP modules and hosting their applications inside IIS. For more information about how to create an HTTP module, see Creating Native-Code HTTP Modules.
Hosted Web Core (HWC) does not support Centralized SSL Certificates in IIS 8.0. Centralized Certificates requires Windows Activation Server (WAS) to create temporary files based on the ApplicationHost.config file. However, Hosted Web Core is not aware of files created by WAS.