When a UAP is built, HiRDB.NET Data Provider's DLL files are not copied to the executable file storage directory. Instead, when a UAP is executed, the DLL files in the global assembly cache are referenced. For this reason, there is no need to have HiRDB.NET Data Provider's DLL files in the same directory as the UAP when the UAP executes.

Publisher policies for HiRDB.NET Data Provider's DLL files are also placed in the global assembly cache. These publisher policies contain rules used during UAP execution for redirecting the version of HiRDB.NET Data Provider's DLL files for the installed version of HiRDB client. Therefore, when a UAP executes, it references the current version of HiRDB.NET Data Provider and there is no need to rebuild existing UAPs.

The following HiRDB.NET Data Provider version is referenced during UAP execution:

• 09-00 or earlier
  UAPs reference the version of HiRDB.NET Data Provider that has been built. To use a newer version of HiRDB.NET Data Provider, you must first install the newer version of HiRDB client and then rebuild the UAPs.
  
• 09-01 or later
  UAPs always reference the HiRDB.NET Data Provider on the installed HiRDB client.
  

The Windows default settings provide that the publisher policies will be applied. The user can add a setting that will prevent redirecting of the version based on the publisher policies that have been placed on the HiRDB client.

This subsection describes how to avoid applying the publisher policies. For details, see the documentation provided by Microsoft.

(a) Using an application configuration file

When you develop a UAP, you can create an application configuration file ({executable-file-name}.config) and place it together with the application. By adding the setting for disabling publisher policies in the application configuration file (<publisherPolicy apply=no/>element), you can avoid the application of publisher policies for each application.

(b) Using the Control Panel

From Control Panel, choose Administrative Tools, then Microsoft .NET Framework 1.1 Configuration or Microsoft .NET Framework 2.0 Configuration. You can avoid application of publisher policies for each application by changing an application property.