<disableFusionUpdatesFromADManager> Element
Specifies whether the default behavior, which is to allow the runtime host to override configuration settings for an application domain, is disabled.
<configuration> Element
<runtime> Element
<disableCachingBindingFailures> Element
<disableFusionUpdatesFromADManager enabled="0|1"/>
Attributes and Elements
The following sections describe attributes, child elements, and parent elements.
Attributes
Attribute |
Description |
|---|---|
enabled |
Required attribute. Specifies whether the default ability to override Fusion settings is disabled. |
enabled Attribute
Value |
Description |
|---|---|
0 |
Do not disable the ability to override Fusion settings. This is the default behavior, starting with the .NET Framework version 4. |
1 |
Disable the ability to override Fusion settings. This reverts to the behavior of earlier versions of the .NET Framework. |
Child Elements
None.
Parent Elements
Element |
Description |
|---|---|
configuration |
The root element in every configuration file used by the common language runtime and .NET Framework applications. |
runtime |
Contains information about assembly binding and garbage collection. |
Remarks
Starting with the .NET Framework version 4, the default behavior is to allow the AppDomainManager object to override configuration settings by using the ConfigurationFile property or the SetConfigurationBytes method of the AppDomainSetup object that is passed to your implementation of the AppDomainManager.InitializeNewDomain method, in your subclass of AppDomainManager. For the default application domain, the settings you change override the settings that were specified by the application configuration file. For other application domains, they override the configuration settings that were passed to the AppDomainManager.CreateDomain or AppDomain.CreateDomain method.
You can either pass new configuration information, or pass null (Nothing in Visual Basic) to eliminate configuration information that was passed in.
Do not pass configuration information to both the ConfigurationFile property and the SetConfigurationBytes method. If you pass configuration information to both, the information you pass to the ConfigurationFile property is ignored, because the SetConfigurationBytes method overrides configuration information from the application configuration file. If you use the ConfigurationFile property, you can pass null (Nothing in Visual Basic) to the SetConfigurationBytes method to eliminate any configuration bytes that were specified in the call to the AppDomainManager.CreateDomain or AppDomain.CreateDomain method.
In addition to configuration information, you can change the following settings on the AppDomainSetup object that is passed to your implementation of the AppDomainManager.InitializeNewDomain method: ApplicationBase, ApplicationName, CachePath, DisallowApplicationBaseProbing, DisallowBindingRedirects, DisallowCodeDownload, DisallowPublisherPolicy, DynamicBase, LoaderOptimization, PrivateBinPath, PrivateBinPathProbe, ShadowCopyDirectories, and ShadowCopyFiles.
As an alternative to using the <disableFusionUpdatesFromADManager> element, you can disable the default behavior by creating a registry setting or by setting an environment variable. In the registry, create a DWORD value named COMPLUS_disableFusionUpdatesFromADManager under HKCU\Software\Microsoft\.NETFramework or HKLM\Software\Microsoft\.NETFramework, and set the value to 1. At the command line, set the environment variable COMPLUS_disableFusionUpdatesFromADManager to 1.
Example
The following code example shows how to disable the ability to override Fusion settings by using the <disableFusionUpdatesFromADManager> element.
<configuration>
<runtime>
<disableFusionUpdatesFromADManager enabled="1" />
</runtime>
</configuration>
See Also
Reference
Concepts
How the Runtime Locates Assemblies