This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!
Application Behavior
There are several application settings that can be configured either on an application-by-application basis, or at the machine level, for all applications launched on that machine. There are rules for how settings at each of these levels are merged to obtain a single set of configuration settings for a given application. The rules for each setting are given in the description of the settings that follow.
The configuration settings available in this release are:
- Application specific search path - the path that the runtime uses to locate assemblies that are referenced during the execution of an application. The application specific search path is relative to the application path.
- Version policy -- for a given application, it is possible to specify as policy what version of a particular assembly should be used, or specify that the application should run in "safe mode," using exactly those versions that it was compiled with.
- Codebase - explicit information about where to find a referenced assembly.
- NGWS Runtime Remoting – the information necessary for the remoting infrastructure to properly expose and consume remote types and assemblies.
Excluding the NGWS runtime remoting, these configuration settings are located in one of two places:
- The machine wide configuration file located at %windir%\admin.cfg where %windir% is the Windows directory.
- The application specific configuration file located in the same directory as the application that is executing. The filename is the same name as the application with a .cfg extension instead of an .exe extension. For example, the configuration file for xyz.exe is xyz.cfg.
In this release, NGWS runtime remoting currently uses its own configuration file. In future releases, remoting configuration information will be included in the configuration files mentioned above.