Revision #2

You are currently reviewing an older revision of this page.
Go to current version

General Configuration

Q: How are default configuration settings inherited by a service?

A: At present, you can set default configuration settings for the server, site, or application that includes a service. When you select the Use default control for the service (in the General tag of the Configure Service dialog box, or by using the Set-ASAppServiceBehaviorName cmdlet), the default configuration settings for the next highest level is used for the service. For example, if you have default configuration settings for the server and application that include the service, the service will use the application defaults, and will not use the server defaults.

Q: Which configuration files contains configuration settings that you set in the AppFabric IIS Manager extensions or by using AppFabric cmdlets?

A: Virtually all configuration settings that you set in the AppFabric UI or by using the AppFabric cmdlets are made in the web.config files for the server, site, application, and service scopes. The configuration hierarchy of these scopes defines the configuration of a service for AppFabric. One exception to this is that auto-start settings for an application are made in the ApplicationHost.config file for the server.

Q: How can I minimize the cost of application domain recycling that occurs when I reconfigure a service?

A: Minimize the number of re-configuration processes that you incur, especially at higher levels. You can do so by configuring server and site defaults before importing and then configuring an application.

Revert to this revision