Configuring Applications
The .NET Framework gives developers and administrators control and flexibility over the way applications run. An administrator can control which protected resources an application can access, which versions of assemblies an application will use, and where remote applications and objects are located. Developers can put settings in configuration files, eliminating the need to recompile an application every time a setting changes. This section describes what can be configured and why configuring an application might be useful.
In This Section
- Configuration How-to Topics
-
Provides links to how-to topics on configuring applications
- How to: Locate Assemblies by Using DEVPATH
-
Describes how to direct the runtime to use the DEVPATH environment variable when searching for assemblies.
- Redirecting Assembly Versions
-
Describes how to specify the location of an assembly and which version of an assembly to use.
- Specifying an Assembly's Location
-
Describes how to specify where the runtime should search for an assembly.
- Configuring Cryptography Classes
-
Describes how to map an algorithm name to a cryptography class and an object identifier to a cryptography algorithm.
- How to: Disable Concurrent Garbage Collection
-
Describes how to specify whether the runtime should run the garbage collector concurrently.
- How to: Create a Publisher Policy
-
Describes when and how you should add a publisher policy file to specify assembly redirection and code base settings.
- Registering Remote Objects Using Configuration Files
-
Describes how to register remote objects in configuration files.
- Specifying Which Runtime Version to Use
-
Describes how to specify the runtime version to use for an application.
- Configuring Security Policy
-
Describes how to configure security policy.
- Configuring ASP.NET Applications
-
Describes how to configure ASP.NET applications.