Adding Configured Applications
The Applications folder can help you to address the needs of individual applications. It's the opposite view of the Configured Assemblies folder described in the "Configuring Assemblies" section. The help screen for the Applications folder shows two entries. The first helps you to add a new configured application to the list. The second helps you to fix the configuration of an application. For example, the developer of an application may design it to use an assembly that isn't available or is outdated.
You need to consider two configured application features. First, you can use the entries in the subfolders shown in Figure 5 to reconfigure an application so it works properly. The Assembly Dependencies folder shows which assemblies the application needs to run (not those installed on the machine). When an application requires an assembly that the system doesn't have, you can use the Configured Assemblies folder option to create a binding to a newer version of the assembly.
Figure 5 Create bindings to help older applications run correctly when they become outdated.
The second feature appears in the Properties dialog box for the application. To display this dialog box, right-click the application entry and select Properties from the context menu. The .NET Configuration tool normally selects the Enable Publisher Policy option by default. However, it's possible that someone could clear this check box, which will affect the security of the application. You could find that the application fails because someone has turned off the publisher policies.